High Resolution (3840x2374) Setting

[MK84]

When running FlyInside FSX at High Resolution (3840x2374) setting I am getting these issues:

Oculus 0.6.0.0 Runtime, FlyInside FSX 0600
- Missing texture tiles over water (Intermittent)
Sometimes the a tile would missing so you have all these water and then in the middle there is a square blue tile.

- Trees artifact (Intermittent)
Trees would sometimes get elongated, and/or drawn on different area like over water for example.

Oculus 0.6.0.0 Runtime, FlyInside FSX 0501
- FSX stops responding, on the DK2 the Flyinside FSX splash screen would appear. (Persistent)
At one point it would stop responding when flying over the exact same place. But it happens in other areas as well randomly. VAS hovers around 3.8GB.

Anyone else running FlyInside FSX at High Resolution (3840x2374) setting? Any issues?

[admin]

I always use the high resolution setting. Like you, I also have the 780 Ti and 16GB of RAM. Are you using an 3rd party add-ons? Also, what are your graphics/scenery levels like?

[MK84]

So far I am testing with these addon's enabled.

Scenery/Environment:
ORBX FTX Global
ORBX FTX Vector
ORBX OpenLC EU
ORBX FTX Wales
ORBX NSTU Pago Pago International Airport
ORBX FTX Trees HD
FreeMeshX
REX4 Texture Direct + Soft Clouds

FSX Settings:






Gonna run some test over the weekend with fresh FSX:SE install.

[Robert]

Hey MK84, I was getting pauses as well where the FlyInside skybox would come up and what fixed it for me was to go back to 0.5.0.1 runtime. I don't know where the issue is when FlyInside 0.17 is paired with 0.6.0 runtime, but I was getting the same behavior and I also run Orbx Global Base, Global Vector, Trees, Pacific Northwest, Northern California, and Southern Rockies, plus various airports, with FlyInside set to high resolution in the settings.

[MK84]

Interesting. Okay rolling back to 0.5.0.1 first then. Thanks.

[Robert]

MK84, in looking at this again, I said that wrong. I was also getting pauses but it's apparently due to scenery loading. I was also getting hangs that were permanent and apparently OOMs (and others where I would get the OOM error message) where the sim would just freeze. Those are what went away after reverting to 0.5.0.1.

But the temporary pauses are probably still there. I haven't had the chance to verify just yet but my short pauses are dead reproducible when I fly a certain course over a certain location. I was trying to do multiple things at once and didn't mean to post misleading information.

[MK84]

No worries, testing continues.

[admin]

There have definitely been some reports of OOMs combining FlyInside with 3rd party scenery.

My bet is that with high resolution, all of those scenery add-ons, and high settings, you're getting close to OOMs so FSX kicks things out of memory and glitches. Could you let me know where your VAS is at when using FSX with all of this, but no FlyInside? I'd like to determine how much FlyInside is raising memory usage by total, in these cases. Also, what techniques are you using to measure it?

Thanks,
Dan

[MK84]

It certainly all add up. I use Process Explorer to monitor VAS, Task Manager for the CPU and GPU-Z for the GPU. I have Shadowplay enabled so if/when error occurs I can save the last five minutes up to that point.

I'll get some comparison done with and without Flyinside.

[Sylas]

These are the numbers from running Flyinside

WithRift.png (121.33 KiB) Viewed 10324 times

I know you weren't asking me, but I was hoping to be of some service. I am running a newly installed, but old standard edition FSX w/acceleration and I'm flying two different scenarios with and without the Rift. I have ORBX Global 1.3 installed, and in one example I'm flying an A2A B377 Stratocruiser (Captain of the ship) departing Palm Springs. The other example is flying a Carenado C185F out of finger lake where it's almost completely flat at the beginning and rather dull, but extremely good framerates with or without Flyinside, but I'll attach those two images in the next post. I'm not entirely sure that my data will even help, because the numbers are so inconsistent...Like how could my CPU usage be HIGHER without the Rift? You would know better than I would. What I did was reset HWinfo to minimums..played the game for 5 mins without the Rift, pulled up HWinfo and took a screenshot. Then let it cool down, reset minimums again, and ran the game in Rift, taking a screenshot afterward. Obviously the numbers to pay attention to will be the maximums. Next I will install REX, and if things go right, then possibly ORBX N.Cal and PNW. I have a feeling I wont make it that far before crapping out though.

Oculus runtime 0.6.0.0 Windows 7 X64 SP1 Intel i5 3570K@4500Mhz, AsRock Z77 Extreme 4, 16GB ADATA DDR3@2400, MSI GTX 670PE 2GB X2 SLI with only one enabled for FSX, 240GB Crucial M500 SSD, Creative Labs X-Fi Titanium PCI-e, I'll fill my sig after this