Cpt. Oveur
-
Posts
74 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by Cpt. Oveur
-
-
Thank you very much Emilios!
-
OK, now: I just completed my second flight in the NGX to LGTS with 'Scenery complexity' set to 'normal'. And again from an VAS-intensive origin (Earth Simulations - Isle of Man). At the end, parked in front of the terminal, VAS usage was between 3.7 and 3.8. No OOM, no Windows warning sound or something like this. I even was able to change my aircraft to the Twin Otter Extended and I did a second VFR flight around the city. Can't believe it !!! And I can live with that changed slider setting.
Emil, thanks a lot for your support! My problem is solved and finally I'm able to enjoy everything!
-
Emil, you wrote 'low' global texture resolution, I tried 'normal' instead and this works! VAS usage after landing was still very high (between 3.7 and 3.8) and maybe only one step away from the worst case, but it works (I used the same conditions as yesterday: identical aircraft, scenery, weather, time etc.). So, finally no warning sounds anymore, no texture loading problem and of course no OOM...
Emil, I don't know why but I used the wrong slider!
I set 'Scenery complexity' to normal, not 'global texture resolution'. Sorry about. Anyway, it works so far. At the moment I make another test flight from Earth Simulations Isle of Man to Thessaloniki. I keep my fingers crossed...@ olli4740: Sorry, but this comparison is far-fetched! And if it's not possible to fly an 'heavy-weight' airliner like the NGX to an 'heavy-weight' LGTS, then Aerosoft should mention it in their product description.
@ Mathijs Kok: Your argumentation is really inappropriate! By the way, I reformated my hard disk already 2 months ago and I'm using a Win 7 64 bit version. But telling me to not use any tweaking (exception: high mem tweak) is kind of ignoring the reality! Nearly everyone is using the Bojote tweak or something like this. I also don't care about polygons, visibility ranges or whatever. I'm the customer, so I'm simply not responsible for that. The area of T2G's MMMX is comparable with the LGTS scenery but obviously they managed it better regarding to the VAS usage. And you exceed your authority by writing 'You are pushing your system over the limit and you are blaming the last product product you added'. Are you an tele-diagnostician ?? You are running down YOUR CUTOMERS in this way, maybe you don't notice that. I will write it again and again: My FSX was running without any OOM since years and now you're really want to say that this is only my mistake?
-
2
-
-
Thanks for the report. Agree all looks good, almost the perfect setup. Not sure how consuming are the FTX add-ons but anyway.
That's why you get 2.65GB, which is a normal reading, and is an overall low memory load which should allow you to normally take-off and land too.
I'd only have to resort to hardware (GPU), inability to render textures (black textures) would certainly fit with that.
Not something I saw during testing though but it is possible, because the method we render the city is 'loading up' the graphics card quite a lot, which allows the fast frames.
What's your GPU specs? updated drivers? any external GPU controllers?
I know it's boring, you could perhaps test FSX with a low Global Texture resolution and try the approach. That could 'ease' the GPU load so we can figure out where the problem is coming from.
Emil, you wrote 'low' global texture resolution, I tried 'normal' instead and this works! VAS usage after landing was still very high (between 3.7 and 3.8) and maybe only one step away from the worst case, but it works (I used the same conditions as yesterday: identical aircraft, scenery, weather, time etc.). So, finally no warning sounds anymore, no texture loading problem and of course no OOM...
-
To support what Emilios wrote: we have simply seen no OOM errors on any of our tests, not one of our 12 test machines (all machines used by personal) ever showed OOM errors.
This weekend I assisted two befriended customers who had consistent OOM errors by logging on to their machines (this is not standard service) and on both machines I found heavily modified cfg files. So we did FPS benchmarks (both in FPS and in FPS variation) before resetting the cfg, adding the 2k and high mem tweaks. In both cases no OOM's where seen and in both (!) cases FPS were higher. In one case more stable, in the other case a bit more variable but that was because the average was over 40.
I'll say it out loud. If you need a 'tweak' of a product that removes 250.000 polygons you really need to start thinking. Certainly if the majority of customers and all the professionals, all the testers, all the people who made videos, screenshots do not need that tweak *. What Emilios released is not a patch, it close to a castration, lol. It does not fix a problem, it simply deletes stuff so the OOM bothered people can use the product. We advise against using it and advise you to sort out your FS!
I also noticed that a lot of people still use FPS limiter in FSX. We do not advise that unless you get at least 50 fps average (above that FPS becomes very unstable and that's annoying). If you get an unlimited 20 fps in a location and then set the limiter to 20 you will in most cases hardly ever get 20. It's buggy, it's bad. And on many systems I have seen it cause memory leaks. External FPS limiters are fractionally better, but we still see no need for them at all. They all use memory and cycles (costing FPS) to prevent the sim from getting the highest possible FPS. They only make sense if you already have problems.
* and of course people will say, but look at the forum to see MANY MANY MANY people has OOM issues. Please believe me, that's simply not true. We have had solid reports of a dozen people and we did sell a few more then that. If this was an issue with the product the forums would be overflowing with hundreds of complaints. The issue is NOT with the product (sure it needs a lot of memory, it's a freaking super detailed scenery, what did you expect?) but with the way some people have there sim running.
Mathijs, with all due respect: I really need to start thinking about what? To be honest, in my case (Emilios confirmed my settings are good) it should be possible to make a flight from A to B without any OOM issues! Today I loaded a flight with the NGX at Taxi2Gate's MMMX Mexico City Xtreme (which is similar on it's area and scale to Thessaloniki) and VAS usage was aout 500 MB lower than loading a flight with the NGX at Thessaloniki.
I say it again: I NEVER experienced an OOM before !!! And I did a lot of flights in the past and own a lot of sceneries...
But now I will repeat my yesterdays flight from EGHI to LGTS with a low global texture resolution and report back later with my result...
-
1
-
-
Have a look at my system profile (orange sysP-logo) via my signature. I don't use the latest driver in this case, because revision number 13.9 causes continually CTDs/black screens in FSX (it's a known bug) so I downgraded to 13.4. which is not much older.
I don't care if it's boring or not - I'll try... if it helps!
-
OK,if I remember right, this would correspond to 'medium' in FSX, fine.
It's rather odd I have to say. I never exceed 3.2GB VAS (LITE II configuration) with NGX on approach.
Perhaps you could give me base value of VAS when you load the NGX (hope you are using the latest updated version?) at LGTS (LITE II) when sitting at the apron?
If that exceeds the value of 2.7-2.8 GB, then definintely there is a lot going on in the background (other settings too high perhaps, water? AI?)
Yes, it's 'medium'. I have a VAS value of about 2.65 GB when loading a flight with the NGX at LGTS. Of course I've installed the latest updates for everything!
Other important settings:
- Filtering: anisotropic
- Anti-aliasing: on
- Global texture resolution: max
- Aircraft cast shadows on ground: off
- Aircraft cast shadows on itself: off
- Mesh complexity: 50%
- Mesh resolution: 19 m
- Texture resolution: 60 cm
- Water effects: Mid 1.x
- Land detail textures: activated
- Scenery complexity: Extremely Dense
- Autogen density: normal
- Ground scenery shadows: deactivated
- Cloud draw distance: depending on the weather situation, between 96km (slider full left) and 176 km (slider full right)
- Cloud coverage density: max
- Airliner traffic: 30 % (Flight1 UT2 2013)
- General aviation traffic: off
- Airport vehicles: off
- Road vehicles: off
- Ships and ferries: 0
- Leisure boats: 0
- fsx.cfg: TEXTURE_MAX_LOAD=1024
- REX clouds resolution: cumulus 1024, cirrus 512
- FTX Global and FTX Global Vector
- Weather add-on: FS Global Real Weather
As you can see, I'm not that kind of person that is running FSX with very high settings, basically they are anywhere between low and medium.
I did a flight from Orbx/29Palms Southampton and FTX EU England to Thessaloniki with the NGX today. Yesterday from Drzewiecki Designs Warsaw Modlin Airport EPMO. All other sceneries were deactivated, but always the same problem...
-
Hi,
What's your LOD radius setting?
LOD_RADIUS=3.500000
-
Emil,
unfortunately the problem remains, even with your latest City Configurator (LITE II configuration)!
But there's a difference: The OOM warning message doesn't appear, but every time when I'm approaching the city/airport I get this particular warning sound from Windows and the textures of FSX stop loading.
VAS usage is still MUCH higher than with similar add-ons...
Repaint request
in Tweaking, repaints, SDK
Posted
Volaris A319