Condor Soaring Simulator

Trinus Forum Forums Games Condor Soaring Simulator


Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #1812

    A long first post with the hopes that there are more than two real-life glider pilots out there using Condor and Trinus Gyre (though it’s definitely a bonus the only other one I know about is the developer of the application!)

    I always struggled with using Condor in any meaningful way (which is most likely due to my lack of dedication to simulation) and thought VR might be a useful enhancement. However, I have zero experience with any type of immersive VR so this is all very new to me.

    Thanks to some advice from loxai I was able to quickly getting Trinus Gyre and Condor working on an borrowed Galaxy S3 (I’m a Windows Phone user) and a ColorCross head mount I got off Amazon. I tested Condor with both a photorealistic scenery that I developed for the area around my flying club and the New Zealand 0.8 scenery. Here are my observations:

    1. The Galaxy S3 has a 4.8″ display that’s 1280 x 720. To me, this seemed very grainy. I could not read the instruments without zooming in. I would assume that a higher resolution display like is in the Galaxy S4 (1920 x 1080) would improve this but I’m hoping loxai or someone mght eb able to comment on the best way to proceed.

    2. Since the Galaxy S3 has a 1280 x 720 screen, I tested this resolution and 640 x 360 in Condor with no discernible results

    3. I used the TrackIR and Fake3D “enabled” setting per loxia and slightly increased the sensitivity of yaw, pitch, and roll

    4. Only after about a hour of flying did I perform a lens calibration. I was surprised how much a change was need to make things look “right” (that is, I could actually read the “race will start in” text at the top left in the Condor window). However, after flying for about 30 minutes and stopping I felt “cross eyed” for a few minutes so I suspect I did something wrong.

    At this point, I would call my experience promising and if a higher resolution phone such as the S4 would indeed work and reduce the graininess then I would be inclined to keep working at it to optimize the experience.

    Finally, I too was confused with the “z-” button label when I tried to remap the lens calibration keys. After unplugging my joystick (MS FFB 2) and restarting Trinus Gyre the remapping could be performed.


    hey fellow glider!

    Trivia fact for everyone else: one of the reasons Trinus Gyre exists is because I don’t get many chances to fly where I live now, so I wanted to get some nice substitute… still, even though I think Trinus Gyre is yielding very good results, it is nowhere near the real deal, and it will never be. No phone or Oculus Rift can replicate the sensation of being airborne, or winch takeoff, or flying in sync to the tow plane, or cross-wind landing, using your guts to feel and chase the thermals, turning and glancing the landscape, the… ah well, this getting too offtopic 😀

    anyway, going through your points:

    1. 720 is certainly too low to see the instruments in Condor, and the only workaround (until I get positional tracking working) is the zoom in you mention (default key Y, for anyone wondering)

    2. For 720 and fake3D mode, the optimal resolution is either 800×600 or 1024×768, the closest available alternatives to 640×720 (which is half the 720 screen)

    3. If using the resolutions mentioned above, you can leave Fake3D to auto. Also, for ‘sitting games’ (flight sims, driving sims) using TrackIR, I think there’s no need to increase sensitivity and just keep 1:1 mapping, but that’s a personal preference

    4. Yes, lens calibration is important, and it is something that varies depending on the headset used. The calibration should help avoid cross-eyed effect (lens/screen centering parameters), but depending on the headset there’s also the option to move the lenses sideways (this being a good option if same calibration/headset is used by multiple users, as each one of us has different IPD, Interpupillary distance)

    I tested Condor with a 1080 phone, using 1152×864 and 1280×1024 resolutions and I can say all instruments looked quite readable (even the PDA).

    Happy landings!



    I’m not sure I understand some of your comments.

    Specifically, when you say “720 is certainly too low to see the instruments in Condor, and the only workaround (until I get positional tracking working) is the zoom in you mention (default key Y, for anyone wondering)” I’m not sure what you mean by your “positional tracking comment”. Isn’t TrackIR positional tracking?

    Also, it sounds like you agree moving to a 1080 phone would improve the experience. Correct?

    Thanks for all your other thoughts!


    The TrackIR protocol definition supports positional tracking (move head up/down, fwd/back, sideways), but Trinus Gyre is only sending rotational tracking (yaw, pitch, roll). Implementing positional tracking is more complex (but I plan to sort it out).

    A 1080 phone will definitely improve the experience, since you will be able to read all the instruments in Condor, although must say this kind of kills the idea of affordable VR…
    Note that higher resolution means lower performance, my test setup resulted in about 45fps:

    OnePlus one phone (great value for money), running in performance mode
    Condor at 1280×1024, TG mode fast and Fake3D enabled
    Using Wifi direct with a i7 3632QM laptop


    Acquired a second-hand Lenovo S960 with 5″ 1920 x 1080 display (441 dpi) recently for relatively next to nothing. Everything working perfectly (at least, using the 12-31-14 server release) under Windows 10 Technical Preview Build 9926. The difference in screen resolution is remarkable (obviously). As you said, instruments are now readable.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.