If i ever get that far i think ill end up having to research how to make apps for android and just get myself a big tablet or two, three perhaps Actually four? I dont think they have ultra wide touch monitors And make an app that just creates the interface automatically depending on which airplane and such
Combat Flight Simulator. Realistic simulation of military aircraft, tanks, ground vehicles, navy ships, world war two vehicles, trains and ships. Free download includes the Caucasus region and Black Sea that encompasses much of Georgia. It Including a Russian Sukhoi Su-25T ground attack aircraft and the famous WWII North American TF-51D fighter....
@sko2408MCG Pro + 200mm extension. 50+50 was the max spring weight I could get.
I know that you're not supposed to use the use an extension with the VPforce.
How would the "throw" difference compare. I like how with the extension I can really throw the stick around and it actually has enough deflection to run into my legs like in a real aircraft.
with extensions, you have to counter unrealistic, wider throw angles with lower axis saturation in DCS. i usually try to match the stick movement with the virtual stick in the cockpit.
With a 200mm extension it works out to like 4.5" of throw IIRC, I did the math out to try to make sure it was somewhat close to the jet when I was designing the setup
Possibly a weird question: what would the software support be like on linux? What programs are required to run the rhino on windows, a custom driver or some standard FFB driver? Is the configuration GUI built using some windows libraries or something like QT? Is the communication with the rhino documented so I could write my own configuration software if needed. I'm really tempted to order one, but would like some indication of how much work it would be to make it work for a sadist linux gamer like myself first.
2 years ago or so when I started, it was a bit more painful, requiring some DLL overrides, modifying some DCS LUAs for some patches etc. I have spent more time than I'd like to imagine debugging it but anything to avoid windows
That document is probably a bit out of date, not all steps are required anymore. The biggest remaining issues are some graphical glitches with smoke trails, some textures and such
The smoke trails seem to be related to tesselation, which I guess doesn't work the way DCS expects it to in wine. (The smoke trails are puffs at evenly spaced points rather than nice thick trails). The textures seem to be related to DCS using some encoding for some textures that isn't supported by wine. For most of the textures, you can open them up in gimp and just re-export them without changing anything.
The biggest problem is a similar bug on marianas which makes the ground pitch black. I think it might be related, but it seems like the textures for that map are compresed and/or encrypted so I haven't found a way to re-export them
Ah shit, maybe (however i doupt they'll care) we could bug them enough to fix that But i doupt theyll care about just a few non-windows guys trying to play on whats simply just a better system than broken-windows