MotoPsycho

Ah, forever helping out, well if your "help" in this thread is an example of what you have to offer, It would explain a lot as to why there are so many with ongoing issues... Another example of your infinite wisdom. As I already indicated two posts above your first, my issue has already been solved. Not only that, but I left my solution for others to see, in hopes it may help them with any similar issues. Is this how you want me to "learn how to read"? :p No thanks, my way is working pretty well for me, thanks. p.s. And you would also be well served to put away your sense of self-importance Mr. 764 posts :rolleyes: all your posts in this thread that are worthless.

Perhaps it is you that should follow your own "statements". Let's review, shall we? ...anyone? anyone? You mean anyone but YOU, right? As this is exactly opposite of your little nugget of wisdom you deposited in this thread earlier. Again, nobody is suggesting BIS is liable for anything, including software that runs on drivers that aren't invented yet - those are your words not mine. But since the 190.38 drivers were released roughly a month ago, and patch 1.3 is much sooner, then any developer will tell you that those drivers have been tested. The post I linked to somewhat confirms that as BIS (or at least their moderators) found it worthy enough to deem it stickyable. I suggest if you have nothing to add to a troubleshooting thread other than your non-essential opinion that contradicts posts made by moderators, It may serve you well to instead, just move along...with that in mind, I offer you a quote from Abraham Lincoln - "It is better to remain silent and be thought a fool than to open one's mouth and remove all doubt. " Have a great day!

LOL - more sage advice? :rolleyes: Might I direct you towards -- http://forums.bistudio.com/showthread.php?t=76908 ...

Jonney, It seems I've solved my GTX 295 issue by running in full XP SP2 compatability mode on the executable, as well as disabling visual themes ( and of course running as admin ) Also - try manually setting your 3D_Performance to 100000, I renamed my arma2.cfg again and again just to collect a few config samples at different settings, and this one by far is the best! http://forums.bistudio.com/showpost.php?p=1402157&postcount=7 [edit] And I am also running the -winxp command line switch. With no mem switch ( I also use the -splash switch but that shouldn't be relevant)

Well let's see.... Nobody expects BI (or any developers) to write for drivers that arn't released yet (even though developers get new cards and drivers before the general public...but that's beside the point) - but thanks for coming to the thread and offering up your help with this sage advice. No offence, but you have no use for an opinion either... :p ( <---that is meant as cynical humor!!) 190.38's came out when? And patch 1.3 when? OK then.... :rolleyes: It's not an nvidia issue, its a game developer's to ensure they write code for CURRENT drivers. IMO ;) .... Anyway, seems I've solved my issue by running in full XP SP2 compatability mode on the executable, as well as disabling visual themes ( and of course running as admin ) Also Jonney - try manually setting your 3D_Performance to 100000, I renamed my arma2.cfg again and again just to collect a few config samples at different settings, and this one by far is the best! Best of luck on getting your 295 sorted out as well! See you on the Battlefields. S!

Hi Jonney, Yeah, Physically it's two banks of 896Mb. And I just noticed my 3D_Perf number was a negative, not a positive number. My DirectX reports the card as having 4079MB so I suspect Arma2 is collecting the vRAM from DX? (which includes a HDD cache)? Might explain why such different values -- *shrug*, just a guess though. If/when I figure it out, i'll update this thread. Do developers ever read this stuff and offer support? Or is it solely up to us users? ---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ---------- If a modern game requires a old driver - I'd rather get a refund. No offence.

I'll be playing and all of a sudden I lose textures, almost everything turns white and FPS goes to chit. Then I get a arma2.exe CTD MY PC SPECS: O/S Vista x64 SP2 CPU Q9650 stock @ 3 GHz 8GB RAM @ 800 EVGA GTX 295 w/ 1792MB vRAM (driver 8.15.0011.9038 + EVGA Enhance 14) Dell 30" Monitor @ 2560x1600x32 res CTD event log info: This is my Arma2 cfg: I should be able to make Arma2 scream on this machine! I can't even get the thing to work with medium settings. CPUID HWMonitor notes GPU temps max at 68C and 71C - so not temp. I'm also running the -winxp switch on the shortcut because of the 8MB RAM ---------- Post added at 11:33 AM ---------- Previous post was at 10:45 AM ---------- OK, just tried some of the advice listed at -- http://forums.bistudio.com/showpost.php?p=1401617&postcount=2 And now my arma2.cfg lists: A jump from 93750 to 4194304 on 3D_Perfomance ? :eek: ....renaming the old config and letting arma2 recreate it was a good step. I'll be back with results after a little MP testing. [edit]: Nope! Still getting the same results!