Topics

I genuinely hate it when people poke my LCD screen, it can cause permanent damage to the display, ESPECIALLY with finger nails or other sharp objects. Today I had a buddy point out something on the screen, and he accidentally rammed his fingernail into the display several times like he would with a CRT. My $1,200 ****ing dollar LCD. I know, you could buy three computers for that price, but I wanted a nice quality PVA or IPS display screen instead of the cheap TN displays. Plus the extra screen real estate really helps me with (school) work.

I'm guessing this is just an old habit because you could poke a CRT until your finger broke and the CRT would have sustained no damage, but the fragile displays of an LCD are far different. With LCD's the display elements are no where nearly as well protected as a CRT's.

I was EXTREMELY irritated, but I did my best to quell my anger, so I just gave him a fair notice to "please don't ram your finger nail into the LCD, it cost over a grand and it is sensitive to kinetic force."

I don't see any damage, fortunately. There's a millimeter-sized dark spot near the center-edge of the screen, but I think that's just crud or something, because I'm sure he assaulted the screen farther away from the edge.

Sheesh, I just can't understand such ignorance from people, which only makes me more angry. I doubt everybody who mindlessly pokes LCD screens is like my buddy who was used to CRT's (although he has been using LCD's for a while, I still don't know why it did not occur to him that he should not poke a $1,200 monitor). But as for the people who mindlessly poke LCD screens for reasons other than being used to CRT's, does anybody know the psychology behind such behavior? There are several "warning signs" for the uneducated that they should not poke an LCD, such as:

1) Irritation from the owners of LCD screens that they poked in the past.
2) The "Newton Rings" that reverberate out from the impact. This can't be good for the LC's, and it should indicate to the assailant that the display elements are right there at the surface, and kinetic force to anything tends to cause physical, or even chemical, change in atomic or general structure, which I assume would be unwanted in an LCD panel.
3) Smudge marks left by oils or food from the skin. Even if an LCD had a glass surface instead of a plastic or matte, it's a major annoyance to have smudge marks on a screen or to clean them.

Edit 1: How come people tend not to pick up on at least one of these until permanent damage to their own LCD or a life-changing encounter with the enraged LCD screen/laptop user?

Edit 2: That dark spot is not crud, it's ****ing DAMAGE! OMFG, I've only had this monitor for a few days !

I'm considering upgrading my video card to either a 9800 GTX or a 9800 GX2 in march. I am considering this over getting a nintendo Wii because I've not heard too many good things about the console.

I expect the GX2 to be a bit more powerful than the GTX. If I got the GX2, would BZII use only one of the GPU's on the card?

Whenever I target any object, any effects like an explosion or a weapon shot seem to "play" at double speed.

However, this speed doubling has more side affects. A very fine example (but again, not the only thing that is affected), is how emitinherit is affected. Targeting an object very adversely affects "emitinherit". I belive that emitinherit values seemingly double, but inconsistently. For those who are curious to know, emitinherit is a percentage of how much speed an emitted object "inherits" from its parent. Here is an example of a fireball I made. The flames emitted have "emitinherit = .9".

Without targeting the scout:


The flames behave normally here. They inherit 90 percent of the projectile's speed.

With targeting the scout:


The difference should be visible even just by looking at the thumbnail. Half of the flames are probably inheriting 180 percent of the projectile's speed. They're (obviously) shooting out in front of the projectile. The other half of the flames seem to be inheriting ZERO percent of the projectile's motion. The effect is massively distorted.

Edit: forum code corrections

I've been trying to get this shot "afterglow" to work, and it required custom geometry. I set the animate time to 5 seconds, yet the geometry only lasted about a tenth of a second. I didn't see a line of code called lifeTime for draw_geom, so I added in lifeTime = 5. That didn't work either. Is there a limit to how long a draw_geom flash can last?

Well... after further testing... it isn'st just draw_geom, it's anything. It appears that the shot flash can last only as long as the weapon shot does. Could this time be extended beyond that perhaps?
Date Posted: July 09, 2006, 11:01:57 AMEdit: After even further testing...

Using the same weapon 1e3 shot speed, with a lifespan of 5 seconds, the shot flash still lasted only an instant, even less time than it took for the weapon shot to race off out of view.

How they love to phase though solid walls of rock, biometal, etc. I'll chase after them, only to end up with a crooked nose! Is there anything that can be done to fix this?

This has been an issue since PB1. Whenever you enter free eye in 1.2, you could use directional keys to move the camera's position on the map. Now, free eye is locked in place on the map from where you place it. You can not travel and distance on the map with free eye in PB1 and PB2. The only way you can move free eye is rotation.

I'm confused. Was this done purposely?

That is, in hovercraft. You probably would never notice it unless you had a hovercraft that could fly in the air about 100 meters or more. Whenever I am not "hovering" over the ground, reverse is pretty much the only direction I can move in. My forward and strafing velocity are extremely limited (probably 1/10 the speed they're sposed to have).

Actually, this has been a bug ever since bzII was made I think.

Whenever you target a friendly unit in first person mode, you're "invisible".

Urgh, I'm not being too optomistic am I? Well, I am liking 1.3pb2 just fyi.

In 1.3pb2 editor. whenever you type in "spawn" for the config, then TAB over (you must tab), type in an object config and ENTER it, then try to place the spawn, you'll always get an "ERROR *****.odf does not exist".

This is the best that I can describe the bug.

Whenever EMBM is enabled, in mission isdf04.bzn, there's terrain .xsi models on it. Whenever you get close and look at it wrong, a scion texture appears on it quite obviously. This probably happens with all terrain (at least pluto terrain).

Edit: Oh, and, terrain must be set to high in graphics.

Edit(CmptrWz): Changed "Major" to "Known" as this is by no means a major bug, and is quite known.

By default, (for example), in the height section. There's a scroller for the height you set the terrain to. It only goes from -3000 to 3000. The true limits are -32768 to 32767. when you set a value higher than 3000, the scrolling "white square" ventures outside of the scrolling "bar".

When placing units in the objects section, there's a scroller that has a limit from -3000 to 3000. I feel that the limit should be increased, especially since if there's a limit, it's a lot higher or lower than -3000 or 3000.

Whenever a light is close to or on the ground (especially noticable on flat terrain), the light is made extremely dim and it for the most part only the light towards the southern part of the map can be seen.

(Can't submit a picture because photobucket won't take my .jpg format file!! They say they take .jpg format files!!).

... then undoing and redoing, causes you to uncontrollably move in that direction. At least I think that's how it's done.

Whenever I use huge sprites, and I get close to them, they slide off the screen (but this dosen't happen if I'm not close to them) (in weapons odf).


BTW, I'm back, but I don't have internet at home.

I notice that the shell graphics menu lies to me on the actual settings during any single player / IA mission. I'm not exactly sure which buttons will glitch, but a very common example for me is that I'll have local fog turned off, and I'll see local fog on the map! I'll have to turn it on and off to get it off. Plus, after finishing the mission and restarting the game (normally), the same thing happens! I'll have local fog off and it's still appearing on the map.

The freeeye camera view (shift+F12) is fixed and can't be moved once activated in 1.3. Is this a bug or was it intended?

Edit: Yes, freeeye can be rotated, it's just that the location can't be changed.

In 1.3, I've experienced problems with landing a craft, and flying an aircraft. I'll begin to speed up slowly, in the direction that the underbelly of my aircraft is pointing, and I'll keep speeding up, increasing in an exponentail rate, I'd say [My Speed]^(2 + (3 more powers every second).

Same thing happens with flying, only my underbelly can face ANY direction, even the sky, even over the lip of the map, and the equation would be [My Speed]^(4 + (7 more powers every second), and this bug happens after I "land. The equations may be a BIG understatement, because I'm traveling faster than 1e6 within 4 seconds.

If you fps drops below 8, it starts to shake, so badly, that it can end up shaking 180 degrees or more around your vehicle, if you have it in 2nd person view or chase. It would be very nice to have the camera shaking eliminated.

(NT)

I dunno if this has been fixed yet, but each time the game resynchs, the nav beacons become deselected, and if you have a nav beacon that isn't named Nav, it will be renamed to nav after a resynch. Pretty much everything that that doesn't get recorded to other players that gets resynched gets reset to its default.