April 12, 201412 yr Pushed it a bit but was realistically hoping it would not fail From KPHL (Sunskyjet) to FSDreamTeam's KJFK with Aerosoft's Manhattan X; AXE; JFTraffic360 at 35% screen resolution was (3 DELLS) = 3150x1680 eyefinity HD7970 3G videocard FTX Global and Vector (update ASN with REX4 (4096 graphics) cloud shadows draw to 20km (100km and max density in settings) terrain shadows 20 km veg and bild dense fps a constant 16 on final after landing.... VRAM maxed at 2.7G (400 for win-7.64 etc.) RAM usage maxed for P3D got to just above 3.2G before calling the OOM flag but was able to continue to the ramp That was a whopping 5.5G max usage for P3D Solution: do not use 4096 textures, might work well with 2048 anecdote: FSUIPC was able to save the situation at the ramp from an autosave... sort of a complete flight then
April 12, 201412 yr You asked for it! Lol Did a similar test flying over the Nyc/NJ area with nycx and fsdreamteam jfk.... .. . Flew about an hour with everything maxed (no shadows except cockpit)... and not a single OOM. And.... Flying up to the city from jfk.. . the whole skyline was in view and never dropped out once. Previously, that flight lasted about 10mins before OOM and all soughts of texture issues.
April 12, 201412 yr Author It worked out pretty good actually, considering the settings Anyway, the act of only reducing the texture max to 2048 was sufficient to replay the trip without even coming close to any OOM And the view from far out is amazing !
Create an account or sign in to comment