Rinning FlyInside drops Framerates to half P3Dv2

[Voodoo]

Hi guys, I am finding that running Flyinside compared to not running it drops frames from 55-60 Average to 25-27 Average.
Am I doing this right or just expecting too much?
1/2 seems like a lot. Also, I am getting out of memory errors when I run FIFSX inside P3Dv2.
Thanks

[admin]

So, it is pretty normal for FlyInside to drop frame-rates significantly. Assuming you're using FlyInside's 4K mode, it's running at much higher resolution (more pixels), and a much wider FOV than normal (more polygons). This means a big performance hit just as a nature of what's being drawn.

Still, 25fps is very low for a Titan. Do you happen to have your settings pegged? I'd recommend dropping them to mid-level and adjusting from there.

[Voodoo]

Well about half already. Do you expect a performance increase with the rift they release to market?

[tyke]

I expect flyinside + 4k res to approximately half my fsx/p3d refresh rates. It's rendering 2 images instead of 1, and at 4k.

[Robert]

But this actually bodes really well for performance as HMD resolution and frame rates increase.

If we can already render at 4k per eye and timewarp up to 75 fps, getting to 90 shouldn't be too hard. Worst case hopefully with people already able to hold 75 time warped fps while rendering at 4k is they may need to just adjust settings down a bit to free up cycles to hit 90 timewarp FPS. There's no guarantees - obviously - but the supersampling kind of gives us a peek into the future and the future looks good if I'm thinking about this the right way.

With the Rift CV1 and Vive both being well below 4k, that's even an easier jump to say we stand a good chance to not have significant performance issues.