FuriousMeow

Are you sure? I think it's the AI that is causing more CPU cycles to be used up. Each multi-crew plane effectively adds one to 3 AI units.

TrackIr just works as long as your software is up-to-date and your game updates in TiR software is up-to-date, there are no settings in Il-2 GB. Start up TiR software and go. I don't center until I'm on the runway. nVidia 3D works as well. Cockpits are 3D, and it gets a bit less 3D and more 2D the further away something is from your view.

Trying to justify making a terrible purchasing mistake and then blaming other people...

Thanks devs and Jason! I haven't updated in over 6 months, just been burned out on games in general, but updated and did some flying/testing today and it's just as incredible as the day I first purchased RoF back in '09. The 109G14 really amazed me and the 190A8 is pretty outstanding! Amazing work guys, truly awesome! Hopefully by the time the P38 or P47 are released I'll get back into gaming/simming - but absolutely truly amazing work!

I think that's it, I read something about better cooling which didn't make much sense.

Madcop, they had several parts of the MiG-3 incorrectly modeled for the 3D model, someone pointed them out, and they were fixed. If there's a problem with the compressor air intake, point it out - it will get fixed. You're acting like's a sin against your bloodline or something. For everyone else that knows the P47 - are those cuffed props and won't that help low speed cooling? In the vertical for example?

There was a nice night with whiskey by a fire.

If you're having stuttering issues, and using VSYNC, try turning VSYNC off, then set FPS Target to "off" and re-enable VSYNC. If you're disabling VSYNC, try setting target FPS to off and see how runs. Then try VSYNC on with target FPS to off. .

Based on a mod that removes part of the rendering? Starting to sound like the days of the Rendition API days where removing things ran well, but worked fine in other APIs from 3D card companies that actually accounted for them.

The engine, for BoX, is multicore. I'd need to see some actual evidence that it runs on single core as it doesn't for me. The VR core issue would then be an API issue if that is how it is running the rendering process. The prop issue I bet is that the API is splitting renders between eye screens. An API issue.

You base that on what? Output is quite fine up to 250fps, fastest it's output for me, so you again - you base this on what? VR is still version 1. It's still in it's own "can we make this work even properly" phase let alone "the best". It's like V1 3D graphics cards. Some worked ok, some didn't, coding to it was hit or miss. It also varied between the, at least 5, hardware manufacturers with their own requirements that could vary by a lot.

Pump the freaking brakes. You are acting like a two year old.

Really? If the API the VR devs use can't properly process output from the software, then it is on their end. If the hardware can't process it, again - it's on their end.

It would seem to be more of a problem with the VR side. Asking a game dev to resolve issues the VR devs haven't is going backwards.