March 26, 201214 yr I used to have see-through vc and HIGHMEMFIX=1 fixed it.Just noticed that now I'm having see-through circuit breaker at a random time during flight.Can this happen even with the HIGHMEMFIX=1? Thanks Jose De Campos London
March 26, 201214 yr If you're still getting close to running out of memory, yes. Reducing autogen or traffic a bit may help. Kenneth Weir My Saitek yoke mod i7 2600k @ 4.7 8GB Gskill CAS7 2x GTX580 SLI Surround + GT520 Accessory Win7x64
March 27, 201214 yr Are you sure you put that line in the right location in the fsx.cfg file? That's strange you would be getting that problem. You should be getting out of memory or crash errors if it was a video card issue. Updated drivers? Updated directx?
March 27, 201214 yr Sometimes simply clicking save in notepad will save the file as fsx.cfg.txt. It's possible the edit never took because fsx is looking at the wrong file.Edit: To answer your other question, I think it's unlikely you ran out of actual video memory. DX9 shadows VRAM onto your system ram & that counts toward the 4gb limit imposed on fsx. Considering that, it's possible that the shadowed VRAM was enough to push fsx over the system ram limit, but it's difficult to say. Have you done any manual edits to Lod radius beyond what the fsx options menu allows? A lot of issues like this are from users pushing their system too hard. Kenneth Weir My Saitek yoke mod i7 2600k @ 4.7 8GB Gskill CAS7 2x GTX580 SLI Surround + GT520 Accessory Win7x64
March 27, 201214 yr Commercial Member AutoGen and AI traffic leak memory. Your best bet is to switch these off - not like you can see them from FL350 anyway. :)Best regards,Robin.
March 27, 201214 yr Commercial Member Proof of that? I've never seen FSX have a constantly rising memory value. (which is what it would have to be for a "leak" in the actual meaning of the term to be there). At one point during testing I ran the NGX for something like 2 1/2 days straight monitoring the memory and it did not constantly go up. High memory use does not necessarily = a leak. Ryan MaziarzFor fastest support, please submit a ticket at http://support.precisionmanuals.com
March 27, 201214 yr I encountered this on one particular livery, QANTAS -800WL I think it was, but not on any other livery. You could try reinstalling the affected livery to see if that helps. Mark Adeane - NZWN
March 27, 201214 yr Author Yes, it happened when I started using BA-800WL, I'll try that. Good shot. Jose De Campos London
Create an account or sign in to comment