FSDreamTeam forum
Products Support => Vancouver CYVR support FSX/P3D => Topic started by: yvesamuel on January 27, 2013, 09:04:43 pm
-
Hi,
I have a rather big configuration (I7 3970, 32 Go Ram, Win 7 X64 on SSD, FSX SP2 on 600 Go raptor, Nvidia 670) and a problem :
When i fly from CYVR (V 1.1): no problem
When I fly to CYVR from the south : no problem (I made a fly KLAX CYVR)
But, when I fly from East to West, I have an OOM about 180 to 200 NM before landing. This hapened with 2 flights, one yesterday EGLL-CYVR on a LVL 767, one just now on a Wilco A320.
I'll have a try coming from West (PANC-CYVR).
I have Ultimate terrain USA and CANDA, GEX installed. I have no ORBX scenery installed.
I suppose the problem is with CYVR because I fly some times to KSEA (Original FSX scenery) and never have such a problem.
Any idea???
Thank's
Yves
-
Your issue is not unlike all the others who have OOM's and probably require you to turn your settings down a bit.
http://www.fsdreamteam.com/forum/index.php?topic=7842.0 (http://www.fsdreamteam.com/forum/index.php?topic=7842.0)
-
I have an OOM about 180 to 200 NM before landing
I suppose the problem is with CYVR because I fly some times to KSEA (Original FSX scenery) and never have such a problem.
The problem doesn't have anything to do with CYVR, because outside 10 NM off the airport center, the *entire* scenery is unloaded, and the whole memory taken by it is reclaimed.
-
H,
I tried this evening a flight KORD CYVR and had no problem.
I'll see around Clagary, must be e problem there.
regards
Yves
-
I have a fairly high end system, i7 2600 CPU 3.4 GHz with 12 GB ram, and started turning off the Active Sky, FTX scenerys, AI aircraft and no matter what I did I was still getting OOM errors.
So the last couple days I have reformatted reinstalled Windows 7 64, and FSX with Accelleration and FSDT CYVR, and FSDT KLAX. Mesh Resolution at 38M, texture resolution at 1M,
Scenery Complexity at dense Auto gen at Normal, Water effects at 0, and no traffic at all or shadows and clear skys. Flew from CYVR to Calgary in the default 737, turned around and flew back to CYVR and
as I pulled up to the gate I got a OOM warning and then the textures started dropping off.
I have gone into LAX with everything MAXed out with lots of AI traffic, Active sky 2012 with REX HD textures on VATSIM, the frame rates would drop to about 15 at LAX but I have never got an out of memory warning.
Just FSX with a fresh Windows install
What do I cut back on now? go any more and it will be back to FS98.....
-
Just FSX with a fresh Windows install
What do I cut back on now? go any more and it will be back to FS98.....
You haven't said the only things that matters: are you using CYVR 1.1 and which texture resolution you set it ?
There's no OOM problem at CYVR at all, there never was, it was just a scenery a bit larger than usual AND it was in an area full of 3rd party add-ons. But the 1.1 version gives you the ability to configure it to take less memory and, if set to lower resolution textures (for example 2048 for ground and 1024 for shadows) it will take less RAM than KLAX.
-
I have now set CYVR to the lowest texture settings and I'll try that, I dont have any 3rd party add-ons installed at this time,
Just FSX with Accelleration, and FSDT CYVR 1.1 and KLAX.
-
Well flew that one, upon arrival at CYYC GSX failed, the menus were there but nothing worked, couldn't restart.
restarted FSX flew CYYC to Vancouver, all worked fine. No OOM on arrival.
-
Well flew that one, upon arrival at CYYC GSX failed, the menus were there but nothing worked, couldn't restart.
Please clarify what do you mean with "nothing worked", what happened when you pressed the CTRL+F12 key ?
restarted FSX flew CYYC to Vancouver, all worked fine. No OOM on arrival.
That's to be expected, CYVR never causes OOM as such, it's only the combination of add-ons used that does, and by limiting the CYVR memory occupation, you are simply lowering the used total, exactly as if you were lowering your settings, or removing another add-on.
-
Ctrl-F12 did nothing, and none of the menu items worked, they were all there though. I had to restart FSX then GSX worked again.
I checked for the error log and there was no log there.
-
I checked for the error log and there was no log there.
The error log doesn't appear automatically, you have to enable logging before starting an FSX session, in order for a log file to be created.
-
So with everything set very low, with no add ons at all, no OOM at CYVR.
Just FSX and FSDTs CYVR.
What do you suggest now?
Is there something can I use to see the memory usage as I run FSX?
I have had no problems with running Active Sky 2012 with the REX textures, FTXs PNW, Ground Enviroment X, Ultimate Terrain X, Vancouver Plus, and the PMDG MD11
and having the sliders almost maxed out. I can't see it as being a machine problem.
-
So with everything set very low, with no add ons at all, no OOM at CYVR. Just FSX and FSDTs CYVR.
Well, the airplane you are flying obviously takes memory. And, even if it's "just" FSX and CYVR, it's possible you are taking lot of memory with your settings. Especially the autogen and the scenery range.
You can use the free ProcessExplorer utility to check how much memory FSX is using.
-
Everything was turned right down and no autogen, default 737 was used.
-
Sorry, but an OOM under those conditions is basically impossible, under XP with a video card with lots of VRAM it might, but not under Windows 64. The only possible explanation is that you have an FSX *module* loaded as a .DLL in the DLL.XML file, that is leaking memory.
There was some paper from Microsoft that warns that, if a program requires the .NET runtime and it's an in-process .DLL (all FSX modules .DLLs are), the whole .NET runtime will use the same VAS as the host process (FSX.EXE) and the runtime requires a large amount of memory on its own, for garbage collection, even if the module itself is very small.
Just to make it clear, nothing made by us requires or calls .NET.
As I've said, you can use the free ProcessExplorer utility to check how much memory FSX is using.
-
It was a fresh install but I'll check out the DLL thing.
-
i am the same club with the OOM´s BUT i must admit that switching to DX10 saved me 1GB of VAS!!!! Thats alot. DX10 might be a way afterall for FSX in the future
Michael Moe
-
I have the same problem. Just bought CYVR and now have OOM problems. My system is pretty good - I7-960(@3.33), 12 gigs fast ram, Nvidia 580gtx, fsx on a 512 gig ssd, o/s on a 120 gig ssd. Never had a single OOM problem before CYVR. Usually when inbound CYVR the buildings and ground textures are gone sometimes followed by the OOM. Not sure what to do as how things are now CYVR is not, for me, usable.
Dave
-
Also, My O/S is Win7-64. On departure CYVR usually dissapears withing a minute.
Dave
-
12 gigs fast ram
Doesn't matter if you have 300GB, FSX is a 32 GB program, which only utilizes 4 GB of Ram total.
Never had a single OOM problem before CYVR
That's because CYVR is an area which is subject to many add ons, and custom scenery objects. (Such as ORBX).
Since Virtuali has said this countless of times, it's not "CYVR" that is the problem. An OOM occurs from the COMBINATION of addons you are using. The solution is simple. You will have to:
- Choose to use a lighter aircraft, or remove ORBX scenery (if you have it installed)
-Switch to lower texture resolution (which was provided in the update)
- Turn down your settings (which you should do anyway)
- Switch to DX10. (Fully compatible)
-
Actually, giving it some more thought....
I've had no problem with OOM issues with any other piece of scenery, ever, on this rig. Problems started after the installation of CYVR (for example - no problems what-so-ever with Fly Tampa Montreal and that's one bear of a scenery for detail too) so the problem is CYVR. I''ve been running test flights from Abbottsford (CYXX) departing RWY25 to CYVR RNAV approach to 26R at night, using FSX fair weather only. I've used two aircraft in tese flights - the PMDG NGX which admittedly is a complex aircraft but I have also used the Eaaglesoft Citation 2 which is very easy on FPS and surprisingly the FPS did not vary significantly. Turning things down some the last couple of flights there were no OOM (there was stuttering approaching CYVR) but there was no fsdt CYVR to be found either - no ground textures, no green lead in lighting of the runway to the taxiways, no buildings, nothing. In Vancouver i run it with Orbix PNW. What exactly is the problem here , I have no idea. I've got more than enough horsepower to run everything else. When in demo before purchase the 3-5 minutes the scenery ran it was spectacular. I hope the situation can be resolved because CYVR is that good.
In the real world I'm not a computer programmer, computer wizard, whatever, but I know when the problem began.....
-
I've had no problem with OOM issues with any other piece of scenery, ever, on this rig. Problems started after the installation of CYVR (for example - no problems what-so-ever with Fly Tampa Montreal and that's one bear of a scenery for detail too) so the problem is CYVR.
No, it's not, and if you followed all the discussion about OOMs, it was clear that CYVR is not the problem, other than that is a fairly large scenery which lies in an ALREADY problematic area, which is taking quite a bit of memory even with default scenery only, but with many 3rd party add-ons available to add.
Is there a similar product such as "Orbx Montreal" or "Montreal city+" ? That's a difference between the two areas. Unless there was *another* comparably detailed scenery for CYVR Airport, there are no grounds for any correct comparison with anything else.
In Vancouver i run it with Orbix PNW
That's what I've thought. So, why, "the problem must be CYVR" ?
Yes, the airport is taking quite a bit of memory, but as explained countless of times here, it's the sum of everything *and* your settings that cause OOMs, it's never a single product. But again, people always put the blame on the last installed product "because the problem didn't happened before".
As explained several times already, suppose you bought CYVR first, and use it only with default airplanes. Of course, you wouldn't see any OOMs. Then buy the PMDG, which is taking more than 800MB for itself, boom...instant OOM. Who's fault is then ?
The correct answer is, none. Or, if you prefer this, the sad fact the FSX is not developed anymore, and we can't expect a 64 bit version anytime.
What exactly is the problem here , I have no idea. I've got more than enough horsepower to run everything else.
You can have all the horsepower in the world, it won't change that fact that FSX, being a 32 bit application, has an absolute limit of 4GB of available memory, regardless how much ram you have in your system.
This means, you just can't expect to keep filling FSX with add-ons, at a certain point your memory is going to end, and there's no other solution than to lower your setting, or use less add-ons in a certain area, or a combination of that.
When in demo before purchase the 3-5 minutes the scenery ran it was spectacular
Of course it does. And of course there's not the slightest difference between the purchased version and the demo version.
I hope the situation can be resolved because CYVR is that good.
The situation has already been resolved with the 1.1 installer, which gives you the option to decide the texture resolution for ground textures and dynamic shadows, which greatly reduces memory requirements.
With ground textures at 2048 and shadows textures at 1024, CYVR still looks good, and will take LESS memory than KLAX. And nobody talks about OOMs at KLAX, because the default scenery there is entirely different than CYVR (the different landclass trigger a way sparse autogen), there's no "Orbx South California" to buy, no popular addons for the city, no pesky Seattle nearby, etc.
-
Umberto,
First off, begore we start throwing rocks at each other, let me clearly state I have nothing but the utmost respect for you and your creations. They are very, very good. Having said that I am being totally honest relating my experiences with CYVR.....I've turned down things, researched "fixes' for the OOM issue and applied them and done numerous test flights to try different settings. I seem to have overcome the OOM issues but occaisionally there are no buildings etc present. On startup one thing I have found that works with my machine is to start up in CYVR with the msfs powered hang glider/ultralight/whatever and then change to the aircraft I wish to fly. Seems to work just fine that way including doing multiple circuits with complex aircraft such as the NGX and Level D 767 for 20 or more minutes with no problems. On startup with the hang glider it may take a few moments for the scenery to get "drawn" but just about all the time there's no problem. I should also mention I've had missing buildings etc at PHNL and the only addon being used there is the Megascenery for the island. Have to see how these "fixes" and adjustments work out there. These latest test have been in daylight. I don't know if night time puts more of a load on fsx and memory.
Relax, no need to get defensive. I want this to work. I simply want to crank it up and enjoy it. If I can get this sorted out okay, and I'm on my way to doing that (I think), I'll be dusting off my credit card to purchase your California and Nevada airports. I use megascenery there.
Dave
-
.I've turned down things
What do you mean by "things"
researched "fixes' for the OOM issue
There is no magic "Fix" for an OOM, no code you can add to your FSX.cfg than can solve an OOM. OOM's are a result of too many recourses being Used in your FSX, and you WILL HAVE to give up something. You can't run everything under the sun, and expect no OOM's.
I simply want to crank it up and enjoy it
You will never be able to 'crank it up' in an place like CYVR (Seattle, JFK), because as said again, CYVR is subject to many custom addons like ORBX.
-
Boone, thanks for the lecture. Most appreciated.
With all due respect in the few days I've been here I've pursued the forums in some depth for information and one consistent thing emerges...... The same problems - OOM, Crashes are occurring to more than a few people on more than one fsdt scenery and have been for some time. I was under the impression that CYVR is compatible with ftx/orbix sceneries however they are being mentioned for difficulties with this product by fsdt Reps on this forum. I'm not BS you - go through the forum. As to "never being able to crank it up" fsdreamteam scenery is the first I've had OOM problems with - and this is an honest statement. I've got approx 200 gigs in fsx running on a 512 gig SSD exclusively for fsx and prior to this everything ran well.
I simply desire to find an acceptable solution for my installation.......then I will buy more of fsdreamteam's products.
-
I simply desire to find an acceptable solution for my installation.......then I will buy more of fsdreamteam's products.
I can only repeat and confirm the solution:
With ground textures at 2048 and shadows textures at 1024, CYVR still looks good, and will take LESS memory than KLAX. And nobody talks about OOMs at KLAX, because the default scenery there is entirely different than CYVR (the different landclass trigger a way sparse autogen), there's no "Orbx South California" to buy, no popular addons for the city, no pesky Seattle nearby, etc.
If that's is not enough, then you will have to start working on the other add-ons, and use their configuration options to lower their requirements. For example, the PMDG offers a lower resolution VC textures, other add-ons might have similar options too. And of course, your FSX settings.
There are no compatibility problems with anything from Orbx (other than possible double objects if not removing some double AFCADs), just than simply an higher than average memory occupation when using them together AND with other products too.
As to "never being able to crank it up" fsdreamteam scenery is the first I've had OOM problems with
That's the only scenery for this area we have.
I've got approx 200 gigs in fsx running on a 512 gig SSD exclusively for fsx and prior to this everything ran well.
It seems you still don't understand: you can have all "free" resources you can, with the most powerful system money can buy, if your COMBINATION of used add-ons in a certain area requires more than 4GB at any given time, you WILL have an OOM, plain and simple.
In fact, it's really less than 4GB, because the OOM message from FSX comes *before* 4GB are really taken entirely. 4GB is the absolute limit for any 32 bit app, but the FSX limit is lesser than that, more likely 3.6-3.7 GB.
And, there's the DX9 issue. Under DX9, a copy of used VRAM is taken from the system RAM and stolen from those 4GB, that's why reducing texture resolution is so effective, because it reduces *both* VRAM and RAM allocation at the same time.
An alternative solution, is to run DX10, because you might be able to afford higher texture resolution.
And, there's another issue which is not very well known, which is .NET runtimes: if one of your .DLL add-ons requires the .NET framework, ALL its runtime will be mapped in the application space, taking away from those 4GB too. None of our products requires/use .NET, but even a tiny module you are running in-process with FSX ( meaning, it's a .DLL ) that use it, and the whole .NET runtime will stole precious VAS space for its garbage collector.
-
Thanks very much for taking the time once again to explain.
Dave