Project Reality Forums

Found it fantastic either way, especially all the new nuggets. Thanks everyone.

ontaiwolf wrote:Hardware or driver glitch, same thing for me.

Well unfortunately in computer terminology they are actually entirely different things.

Perhaps you would like to use a debugger and ascertain the root cause for the error as it occurs at the moment of rendering ? Would be very helpful. A lot more use than guesswork anyway.

Nice vid swedge, had fantastic time playing both maps and thanks goes also to FOB squad, they did great job.

Mod is shaping great and DEV's did real great job on thisone...I'm off to play some more now!

Cheers Swedge! Loved it!

[R-DEV]Twisted Helix wrote:Well unfortunately in computer terminology they are actually entirely different things.

Perhaps you would like to use a debugger and ascertain the root cause for the error as it occurs at the moment of rendering ? Would be very helpful. A lot more use than guesswork anyway.

What debugger? You need a debug build to debug the game.

I just saw the glitch once because you don't see an exploding FOB that often. But you can start a developer session with other developers and test it a little bit. I mean, some of them could build FOBs on different places (on hills, near trees or rocks etc.) and the others could destroy it with different weapons (rpg, satchel charges) from different angles.

ontaiwolf wrote: I mean, some of them could build FOBs on different places (on hills, near trees or rocks etc.) and the others could destroy it with different weapons (rpg, satchel charges) from different angles.

You really think this would help ? And find the problem ?

[R-DEV]Twisted Helix wrote:You really think this would help ? And find the problem ?

I don't know but it's a try. When you are lucky you can at least figure out when the glitch happens. Well it is a better method than just hoping that someone will tell you everything.

ontaiwolf wrote:What debugger? You need a debug build to debug the game.

I just saw the glitch once because you don't see an exploding FOB that often. But you can start a developer session with other developers and test it a little bit. I mean, some of them could build FOBs on different places (on hills, near trees or rocks etc.) and the others could destroy it with different weapons (rpg, satchel charges) from different angles.

I you play the map you see in the first part of Swedge his video( 2 posts above yours) you will see it pretty much every game and as far as i know everybody sees them so i am pretty sure it it not hardware related. As soon as FOB get blown up on that map the game will start show black lines coming from the remains of the FOB.

Jizzed my pants! Cant wait! Looking forward to the new release.

Cant wait new vid from tonight's play...epic fights on Chernarus, but a bit less teamwork at start.

GG all

ontaiwolf wrote:Well it is a better method than just hoping that someone will tell you everything.

With your valuable insight you should be a Dev ....

[R-DEV]epoch wrote:There is an issue that seems linked to the 'bunker' forward outpost (the one with the mound of dirt and the sandbags). Seems to cause a graphic glitch sometimes, and normally only when it's been destroyed. We have not pinned this bug down, so it is not fixed. Happens to me from time to time on my NVidia GTX 560Ti

Ok mate, lets just hope with a bit of luck the new release might magically solve it
If not back to BAF sadly

Try the video card memory flush method when you get it happening. Thats ... LEFT SHIFT + NUMPAD MINUS (press them together), and then type ... flush ...

You should get the screen going dark, and then a message appearing saying the flush is activating, and then it goes into "receiving" ... like when you change your video settings. This apparently sorts it.

I have had someone beside me saying that they could see it, and yet I could see nothing. Its most likely (if the above method works) to do with a memory leak in the shaders, what flush does is clear your video memory and the unusable memory areas caused by a leak.

The exact reason why the effect is caused, could be due to the fire effects, or it could be due to unoptimized geometries using up memory fast (and therefore people with less memory on their video cards get it happening sooner and more often than those with more).

Installed arma2 beta patch 89025 first as recommended... succesfully(at least pr 0.1 starts)
Then installed pr 0.15 with '-beta' option... but it doesn't start! says I got 1.59 version but not 1.60
WTF??!

georgysb wrote:Installed arma2 beta patch 89025 first as recommended... succesfully(at least pr 0.1 starts)
Then installed pr 0.15 with '-beta' option... but it doesn't start! says I got 1.59 version but not 1.60
WTF??!

Either you haven't patched to version 1.60 of the game or you had an old beta from v1.59 which you didn't delete prior to installing the beta for 1.60. If this delete the beta folder from within your Expansions folder and reinstall the beta.

P.S. This is support issue, next time raise a new thread in the correct area https://www.realitymod.com/forum/f449-pr-arma2-support after you have searched it as you would have found your answer.

[R-DEV]Twisted Helix wrote:With your valuable insight you should be a Dev ....

I'm a dev. And if I find a bug in my software I fix it by myself and don't aks users to "debug" it.

Right. Keep in mind this is BETA, alrighty. Create your own thread please, stop 'spamming' the release thread, thanks .