Crash to Desktop after 10-15 minutes...

[Scarmax 10]

Is anyone else having a problem where the ToH Beta crashes to desktop after about 10 or 15 minutes of playing? It's the same almost every time... works fine for about 10 minutes or so, then suddenly the frame rate drops to about 2 or 3 fps for about 15 seconds, then it freezes completly and kicks back to the desktop with the standard "This program has encountered a problem and needs to close" error dialog crap.

I've tried different video settings in the game, video card settings in the nVidia panel, re-installing ToH beta, updating the video drivers... nothing has worked and it's been like this since I first installed it. I know it's a beta, but it's hard to playtest something that won't run for more than about 10 minutes at a time!

- S -

[DarkCrow 10]

Yeah I can't play for longer than 10 minutes either. Mine isn't giving me an error message but just minimizes and I can't bring it back up. I can still hear it though. When I pull up my track ir window afterwards there is always an error with it. This doesn't happen to any of my other sims that I use my track ir.

[gossamersolid 155]

What are your specs of the computer you are playing on?

[buznee 0]

This seems to be a common problem. Happens less frequently once I lowered the graphics. View distance and object detail. I think the beta is just not very stable right now when loading up the sim with too many things to do.

[Scarmax 10]

Ah yes, my sytem specs... here you go.

Intel Core i7 920

nVidia GTX-470 1280MB (driver: beta 285.38)

12 GB DDR3 1600

Gigabyte X58A-UD3R motherboard

Windows 7 Ultimate 32-bit

I know that even though I have 12 GB of memory installed, the 32-bit OS will only use about 3 GB of it. I have 12 GB because I also run a dual boot 64bit Win7 install for other purposes. No, I haven't tried installing ToH on the 64bit side, but I'm starting to think I should just to see what happens.

Yes, I'm using beta video drivers, but before I installed that version, I was running the latest WHQL drivers (v280.26) and was having the same issue with those too.

Thanks!

- S -

[OMAC 254]

I would go back to 280.26 WHQL driver. The beta 285 series have TDR-related CTD problems (which NVIDIA will try and fix for the next WHQL driver). I do get some soft, flushable CTDs using 280.26, but they are not as frequent as you have described.

If your game crashes, you should send dumps to Dwarden:

http://forums.bistudio.com/showthread.php?t=110823

[Scarmax 10]

I went back to the 280.26 driver today in 32-bit Windows, but ToH still crashed after about 10 minutes. So, no change there.

On the other hand, I did install ToH on my 64-bit Windows and I was able to fly around for over an hour without any crash issues. The only odd thing was that textures on buildings looked awful until I got right next to them. It's like it wouldn't load the high-res textures, even though I had both the Video Memory and Texture Detail settings on "Very High".

I think that's an issue with the 64-bit drivers though, like they're not optimized or something. My video card also runs about 15-18 degrees hotter (under load) in 64-bit Windows with the same driver as the 32-bit Windows. (280.26)

But at least I was able to determine that running ToH under 64-bit Windows with 12GB of memory does not crash... for whatever that's worth.

I'll see about sending the crash dumps (for the 32-bit side) to Dwarden, as OMAC suggested. Thanks!

[.kju 3245]

What did you set video memory to in the ingame video options?

[dale0404 5]

What did you set video memory to in the ingame video options?

even though I had both the Video Memory and Texture Detail settings on "Very High".

There you go.:)

[.kju 3245]

Thanks missed your update.

Did you try to set them to default (or low for testing)?

[buznee 0]

Mine are at default and it still crashes once in a while.

[.kju 3245]

Well for some default causes issues, while for others only default gives stable results.

So you have to test it yourself and see what works best.

Finally share yours experiences with others here. :)

[OMAC 254]

Well for some default causes issues, while for others only default gives stable results.

So you have to test it yourself and see what works best.

Finally share yours experiences with others here. :)

PvPscene,

What issues have your heard vidmem=default causing for people? CTD's?

I've only used default for quite a while. Stability is overall good, but I do get occasional CTDs.

Cheers,

OMAC

Scarmax,

Have tried setting AToC=0 in your C:\Users\You\Documents\Take On Helicopters\TakeOnH.cfg?

Edited October 16, 2011 by OMAC

[Scarmax 10]

Scarmax,

Have tried setting AToC=0 in your C:\Users\You\Documents\Take On Helicopters\TakeOnH.cfg?

Hmm, no I haven't tried that, but today I switched the in-game Video Memory option to "Default" and that seems to have fixed the issue with the low-res textures for now. Still haven't had a CTD in 64-bit yet.

What does the AToC=0 trick do?

- S -

[OMAC 254]

I'm glad x64 works better for you.

See .cfg details here, including AToC, which filters veg textures.

http://community.bistudio.com/wiki/arma2.cfg#Languages

This is the ultimate description of AToC:

http://forums.bistudio.com/showpost.php?p=1998153&postcount=42

[boneboys 0]

I set everything to high (including vid mem) and had no problems.

I then set vid-mem to default and the game crashed.

Gone back to high vid-mem,,, no crash.

I understand that this is going against the flow but thats what happened to me.

E8400 à 3.00 ghz, W7 64 bit, 3 go ddr2 ram + gtx460 1go.

oh! 22" SM 2232BW screen at 100%.

Thanks.

[liquidpinky 11]

I set everything to high (including vid mem) and had no problems.

I then set vid-mem to default and the game crashed.

Gone back to high vid-mem,,, no crash.

I understand that this is going against the flow but thats what happened to me.

E8400 à 3.00 ghz, W7 64 bit, 3 go ddr2 ram + gtx460 1go.

oh! 22" SM 2232BW screen at 100%.

Thanks.

I previously ran on the High setting with my GTX285s, it seems to be a good setting for cards with around 1GB of memory or less. Setting above it tended to lead to problems.

[Scarmax 10]

Thanks for the links to the AToC descriptions! I might fly around in the beta a little tonight, so I might tinker with the cfg file and the AToC a bit while I'm at it.

Lataz!

[royaltyinexile 175]

Hopefully..

• This Post
  
• This Thread
  

Should be useful for Sprocket users experiencing problems described here.

Best,

RiE

[Scarmax 10]

Nope, sorry. Those experimental patches didn't resolve the crash-to-desktop issue in 32-bit Windows. I flew around for about 6 minutes, and then it started to stutter as it was trying to load textures, dropping to less than 1 frame per second briefly, then crashed.

Bummer. Right now, I'm just going to plan on running the full version in 64-bit when it gets released.

Edited October 24, 2011 by Scarmax