BG2518 wrote:fen (if I may call you that - lol),
I appreciate your offer of help. Frankly I'm too far gone to be resuscitated.
However, I have given up on FI as a long-term integration to P3D. It was interesting whilst I tried to use it but its not proving to be my go-to solution to VR in P3D.
Yes, when I could get it to work it was good but that's the point, conspiring issues and most NOT directly FI related were "always" at play and the developers must be bald by now.
The early days of flightsim seemed to have the program pretty fixed and running off of a pretty fixed O.S. and thus we all had a fairly stable environment to work with. I could pick up the sim, use it successfully and go back to it 6 months later with no issues.
Not only have I given up on FI but I'm 95% there also with P3D / Win 10 / Nvidia etc etc etc.
I see a glimmer of hope though in a new SIM that FI may be working on?
IF that SIM can be completely independent of Windows O.S. and be bootable (Linux?) then we may have a SIM that can once again be stable.
As of March 2017 - HTC Vive is actively working on Linux support!
Booting to the app was the way originally to make mission critical apps. The PC would be A DEDICATED SIMULATOR.
Hey ho, thanks again.
I agree with you as far as the amount of wasted resources, redundant code and legacy crap in Windows. Its probably less than 30% efficient. I'm a control systems Engineer by trade, the OS I worked on mainly was UNIX (Solaris). We couldn't even use windows based machines at all for critical control systems. The first time we employed windows, was NT4 and that was just for dumb terminals running an X-Windows emulator. However as hardware has progressed and got more complex, accessing things like the GPU is really difficult without going through GUI OS drivers. Basically the hardware has to connect via the OS. Its been probably 20 years now since anything like a graphics card came with DOS drivers. The programmer is essentially isolated from hardware now more than ever. This is the same with Linux, which is essentially UNIX in a party frock. So forget any ideas of a simulator being written in assembler that interfaces directly with the hardware. Its just so complex and the information isn't publically available from the manufacturers to access the hardware at the levels needed. Plus there would be literally millions of hours of development required.
With every new version of an OS comes more crap most of us don't need bogging it down. Unfortunately this is also now starting to happen with the VR hardware too.
The best we can hope for is a ground up sim application that efficiently interface's through the OS with no legacy code.
Tying it to just Linux however would be commercial suicide, but a level of portability would be great.
You can still build a dedicated PC and if you know what you are doing customize the Windows setup to remove as much as possible the things you don't need. Its not ideal like you suggest, but it can bring in an extra 15 to 20 fps and certainly more stability compared with a default windows installation.
Win10-64, i7-4790K OC to 4.7GHZ, 16GB DDR3, EVGA GTX1070 8GB OC, 1 Monitor , CV1, Saitek Rudder Pedals, CH Eclipse Yoke, P3DV4.5
FI P3DV4 Beta Tester. FlyInside Moderator.