Vision Jet bugs

Ouch… I am afraid we will never get a complete VJ… But I will still enjoy flying it. :wink:

I do hope they will fix the obvious bugs though, like the annoying TAKEOFF EMER BAT caution, and add the IPS STALL OFFSET RESET. A lot of the other things in the list are really missing features, not bugs, so I can live with that (for now, haha).

BTW you can of course change the speed in the terminal area to 180 yourself on the VNAV page. This setting will be saved.

And the VNAV target: can’t check it right now but I thought it was 240 and should be 250, so the other way around?

I also wonder what you think of the new default view (pilot cockpit). It seems as if you are sort of lying in the seat, looking up a bit. I tried to get used to it but finally created a new default view, based on a few real life viseo’s. I might post a screenshot later on.

But well, I do like the improvements and the VJ will definitely remain the only plane I fly!

My personal new default view:

And when I look down just a little bit I can actually see the white dots on the buttons (at least enough to see which ones are on or not).

I personally prefer this over the (imho) way too low new default view: it’s as if you are lying on your back almost and looking up…:

With the new default view you hardly see the runway when taking off and you can’t see the white dots at all unless you move forward and up a lot. And it just looks odd imho… As if you are using some sort of fish eye lens almost.

But well, luckily you can change the default view to your own liking. :wink:

I took this screenshot from a guy who has a lot of video’s from moving VJ’s from Cirrus to for instance Australia. (His video’s contain tons of information for those who are interested: https://www.youtube.com/@johnpage8364/videos). @RISCfuture do these default look about right to you? Afaik this guy is moving a brand new VJ so I don’t suppose he would have changed all those settings.

according to the changelog:

Some more…

  • FUEL PUMP ON CAS should be advisory, not caution
  • BLEED OFF CAS should not display when engine is not running
  • DOOR OPEN MAIN, DOOR OPEN EMER, DOOR OPEN BAGGAGE CAS messages should be advisory before engine is started, then warning after engine start
  • In the sim, PROBE HEAT OFF and OXYGEN OFF CAS cautions appear during engine start (and cause a caution alarm). PROBE HEAT OFF should be displayed at all times, and OXYGEN OFF should be displayed at all times (white when engine is stopped, yellow when i’ts running). There should ideally be no caution bells during a normal engine start (though sometimes I get sprious WING/STAB IPS FAIL cautions during engine starts on my aircraft).
  • Moving ALT knob when active vertical mode is ALTS should change active mode to PIT
  • FMS airport elevation should always exactly match the charted airport elevation; in the sim, I see (e.g.) 300 feet chosen for FMS airport elevation when Memphis is 341 feet.
  • Landing lights should wig-wag when gear is up.
4 Likes

Ouch again… I do hope the developers read this too! Do they read this topic, I wonder? I doubt though of they will fix all this because in the end this is a default plane… one of the many. I really hope they do though. Knowing so much is still wrong does spoil the fun a little bit, haha!

1 Like

The bugs i found out how to fix on the vision jet.
cabin lfe not set- send route to avionics in efp

fuel pump on. - switch to right fuel pump. the button is behind the throttle lever

reset the game after every vip mission or it will get buggy

Has anyone noticed that when activating the strobe lights, it also activates the landing lights in an alternating “pulse light” manner? I tried looking for LVARs to map only the strobes, but I can’t seem to turn on just the strobes by themselves.

This is normal behavior.

Good to know. Thanks. I wonder if pulse mode can be disabled. The pulse lights are way overbearing at night and especially in the clouds.

The AFM says that you should turn off strobe lights when in the clouds at night. That should also disable the pulse landing lights.

1 Like

In the future, please create one topic per bug, as it will be unclear if all bugs mentioned in this topic are fixed once we close it.

Bugs created for the following:

  • Pressing BARO knob to set it to STD should not show the PRE field until the knob is rotated
  • Weather radar should start in STANDBY, not OFF (also not implemented)
  • Pressing HDG when NAV is active should set HDG SYNC mode and center the bug
  • Waypoint Info → Weather should show options for METAR (raw), METAR (decoded), TAF (raw), TAF (decoded)
  • PERF page should show an error and reject the value if you enter a required landing distance > available landing distance
  • Vr should be editable but pop an error if any value other than 85 knots is entered
  • CAS display should not have a “CAS 0↑ 0↓” line
  • INIT: Taxi fuel should default to 12 gal and reserves to 70 gal
  • ECS should set DEFOG to on any time generator 1 power is not available. DEFOG can be turned off a few seconds after GEN 1 comes online
  • If ECS Disable is not pre-set from the last flight, the fans should rev once after BAT1 is turned on
  • ISA shouldn’t be displayed on PFD (only available on STATUS page)
  • ELT switch should be in ARM
  • Music button should be underneath Services button, with other buttons: Phone, Connext, Bluetooth, etc.
  • No HITS
  • Green donut too close to stall region
  • Green donut should change dynamically based on g-loading
  • FUEL PRESSURE LOW warning should not show when engine is off
  • BLEED OFF should not show when engine is off
  • MSA missing from available data fields
  • BLEED OFF CAS should not display when engine is not running
  • DOOR OPEN MAIN, DOOR OPEN EMER, DOOR OPEN BAGGAGE CAS messages should be advisory before engine is started, then warning after engine start
  • In the sim, PROBE HEAT OFF and OXYGEN OFF CAS cautions appear during engine start (and cause a caution alarm). PROBE HEAT OFF should be displayed at all times, and OXYGEN OFF should be displayed at all times (white when engine is stopped, yellow when i’ts running). There should ideally be no caution bells during a normal engine start (though sometimes I get sprious WING/STAB IPS FAIL cautions during engine starts on my aircraft).
  • Moving ALT knob when active vertical mode is ALTS should change active mode to PIT
  • FMS airport elevation should always exactly match the charted airport elevation; in the sim, I see (e.g.) 300 feet chosen for FMS airport elevation when Memphis is 341 feet
  • Landing lights should wig-wag when gear is up

Fixed and/or not able to reproduce in latest SU2 Release:

  • IPS Stall Offset reset not implemented
  • Should be able to arm A/T, a lateral mode, and a vertical mode on the ground while TO/TO is active
  • Checklist view should have associated Checklist page on GCU which allows selection of normal/abnornal/emergency checklists as well as resetting checklists
  • No “Confirm” for FOB Sync
  • Switching active pane should switch active page on GCU2 (this doesnt always happen when it should)
  • When an approach is loaded and GPS is active, NAV1 shadow bearing pointer/glideslope pointer should be displayed, and NAV1 frequency and ident should be shown on PFD
  • Checklist scroll wheel reversed
  • FLAPS ICE should inhibit flaps 100
  • Disconnecting F/D on the ground after an ILS shows LOC in both lateral and vertical FMA section
  • FUEL PUMP ON CAS should be advisory, not caution

Other comments

  • A/T should drop speed to 180 when in the terminal area: The Terminal Area Speed Limit setting is defaulted to 200KT, which aligns with FAA speed limit requirements. Tested and confirmed that in V0.5.0 A/T properly sets airspeed to the chosen Terminal Area Speed Limit.
  • Flight planner should be in gallons, not pounds: Trip planner is disabled (INOP), however there is an option to change fuel units between gallons and pounds for other
  • Display Backup not implemented: Labeled as INOP
1 Like

Hey guys, a few dumb questions if I may…

#1) In MSFS 24’ does the weather radar tilt/bearing work at all (I am so sorry if this was already asked before, just couldn’t find it…)? On mine, the GTC #2 screen’s upper knob “push” clickspot has no effect whatsoewher when pressed…so how do I then make it work as it is quite critical for the flights. As per Garmin’s perspective touch+ pilots guide for the SF50+, page 445, I know it should be there, but it isn’t…or is it?

#2) How realistic is the “Realistic” turbulence setting in your opinion? I finished a few flights with it, coupled with the RealTurb CAT Areas addon working in the background…and it seems a bit too wobbly, I mean surely there must be a big box of sick bags stored somewhere on the plane, “as standard” if it is that bad in real life. But from what I know, in reality, it isn’t that bad at all, and the aircraft is actually quite stable, so what would be the most suitable “Turbulence” setting for this?

#3) Is there a way of displaying the “FLT ID” box at the top right corner of the PFD screen?

Has anyone experienced a GTC screen #2 bug after clicking "home button when in Avionics settings menu? It happened to me twice on a cruise. So, for example, while in a cruise, go to Avionics settings, change radio spacing from 25 kHz to 8.33, click “home”. You will likely end up on a blank screen where only a few buttons work, home/back INOP, middle buttons dead! I can’t switch panes, can’t zoom in the map on the right, but I can split the MFD screen still. Very weird and hugely annoying thing, even switching the batteries off in an attempt to fix the screen did not help, had to quit and restart my Vatsim flight because of that!

apparently there’s access to tilting and altitude slices via the legacy JavaScript API, but since this has serious performance issues the high-fidelity airline developers use WebAssembly instead, which only supports a canned 2D top-down bitmap which can’t be tilted. there are reports of one or two payware GA aircraft which use the JavaScript interface and thus can tilt the radar, but no study-level airliners at this time. in fact, many of them have the radar marked INOP, because the devs don’t consider the 2D bitmap realistic enough (a fair appraisal IMO).

some professional airline pilots’ opinions:

@flightdeck2sim:

@320simpilot:

Thank you! Did not expect the radar being so “restricted” in FS24…wow.

1 Like

I would think setting up bindings in the control panel for the Run knob and the Start/ Stop button wouldn’t be to much to ask. Some of us older folks are not comfortable with using programs like SPAD. Next and such.

There are a boatload of inaccuracies here:

  • The JS API is not legacy. It continues to evolve and is a primary API in 2024 just as it was in 2020.
  • The choice to use WASM or JS is really up to developer preference. WASM uses C++, which many developers already had codebases in from previous simulators (FSX, P3D), so those developers often opt to stay in C++. But it is just as possible to code a performant aircraft in either stack, with the appropriate techniques.
  • The weather WXR graphics API available in JS and WASM are identical to each other
  • The weather WXR graphics API in both stacks is not a top down 2D map as was claimed on various YouTube videos and by some developers; it is in fact a correct three dimensional conical section of the projected radar beam returns in front of the aircraft, and supports custom colors, gain, and both horizontal and vertical scan modes. The only feature it doesn’t presently have is tilt
1 Like

that’s good to know. thanks!