In US Dollars, it’s less than what I pay for lunch every day. If I come home for lunch tomorrow, that’s covered. But it’s worth it to me to have all of my current payware planes receiving updates from just one location. All I have to do is launch the Orbx app and check the list. Also, there’s no DRM with Orbx installations.
Haha. Well I wasn’t saying I’m not buying it coz of that. Was just a question. I did get it today from Orbx
Asobo just needs to enable NanoVG for XML gauges by default. You can turn it on in dev mode and you won’t get any FPS drop. I think SWSs position is they aren’t going to completely rewrite the gauge when Asobo is going to eventually turn on NanoVG. It’s the same thing for the DC-6.
I ended up buying this because I’ve been flying the VL3 which I find pretty comparable in terms of ease of use/style a lot lately and then all of a sudden this came out.
Enjoying it so far. The view out front is great, although it does make those panels harder to read at 1080p. I feel like the default height is a bit too high though especially if you look over at the passenger. Flies and performs well but I’m struggling to trim it out for level flight.
I’m terrible with tailwheels so the tailwheel version will be a good one to practice in.
As a VR flyer I was slightly dissapointed to hear that vr cockpit zoom has been left out in this plane. It really helps when using the glass cockpit and renders the plane a little difficult for those of us who can’t lean in close to the panels. Kodiak included it and I purchased it expecting it to be included here.
Any chance of including it retrospectively SWS?
An ultralight with the default cartoony looking G3X? Not for me, I guess.
The problem is that we don’t know how we did it in the Kodiak.
Regarding dimming the G3X, it has been noted and will be checked, as will the other bugs reported!
The autopilot switch isn’t mapped to the button on my joystick. I can engage and disengage using the button on my stick but the switch in the cockpit doesn’t move.
I believe the switch is to give the AP power, not to turn AP on in order to use. First you give it power, then later in flight, you turn on the AP. If that makes sense.
Ah ok, although it doesn’t seem to matter if it is on or off then.
What a sorry mess. Somewhere in the SDK or the software itself, must be a parameter that just needs setting to 1 (I know, gross oversimplification, I have scoured the SDK myself and can find nothing)
The question is, what can be done about it?
I guess, the interested parties (me and other vr users who care) must lobby Microsoft/Asobo to figure out what needs to be done and lay it out in a clear and concise way that developers can clearly see it.
Out of interest, I discovered a couple of mini issues whilst flying a few minutes ago.
-
The small PDF still refers to the plane as the SWS Kodiak.
-
When in VR canopy open shows as closed in external view and when switching back to 2d, canopy is just closed, requiring opening again.
Sorry, also forgot to mention. The plane is absolutely gorgeous to fly and thanks to the devs for a lovely aircraft at a very keen price.
I agree 100% with your comment. Personally I find glass cockpits almost unusable without the zoom and the same for gps units in steam cockpits. Like you I feel that developers need some guidance from Asobo to facilitate this feature. At present there are several aircraft that I would like to own, but will not buy until VR zoom is implemented.
I believe the button controls power to the AP. To engage the autopilot or change which modes are active, use the G3X’s touchscreen – tap on the dark AP bar with rounded ends in the center near the top of the screen (it’s hard to notice initially because the letters “AP” don’t show until you turn it on ) and then hit “AP” on the menu to engage it, and set any modes you want (ALT, VS, NAV, whatever)
Also I recommend using the Working Title G3X enhancement mod for any G3X-using plane:
https://www.workingtitle.aero/packages/g3x/
Only issues I actually found with the plane were;
- Floor mats flicker through the canopy light
- Brightness on the Garmins when set manually to 0 is still like 100% too bright on high NIT display panels at night. In fact it barely dims at all setting to 0.
I will most certainly be flying this again today I already miss it’s gnarly little bored out engine sounds!
With the utmost respect, I think SWS are in a perfect position to solve this riddle for us. They have one plane that has it working (kodiak) and one plane that does not (RV14) Surely with a bit of detective work, one of your developers could figure out what is different about the Kodiak? If I knew what I was doing, I would love to take on the task but sadly, I do not.
I agree with the comments on the g3x brightness. That is honestly the only fault I have found with this aircraft, and it really is a ton of fun to fly for only around $17 US dollars!
Just my opinion but, I think SWS has been one of the few to get the default camera height right in MSFS (both Kodiak and now RV). It definitely is a bit of personal preference, but a pilot’s typical sight picture should be out of the cockpit in level flight. You should have to “glance down” to your instruments and most msfs sight pictures put you on level with the instrument panel. I’m also a Track IR user so that certainly helps since I can simulate that look down very easily.
Just packaged a fix and send it for testing to the team. It will not address anything FM related, but fixes all the systems bugs reported so far and maybe the VR zoom issue.
If all goes well, you will have it next week before we disappear on a break.
Thank you! The RV-14 is so much fun!