In the elevator sense the stick force varies as the square of the speed. In the aileron sense the stick force is constant but the amount of deflection available is decreased gradually from 150kts.
Yes, the controls are centred but there is a mach trimmer which comes into effect above 0.88M on the real aircraft and adjusts the stick aft. Unfortunately, the mach tuck has not been able to be as precisely built as it was in FSX/P3D, so the effect probably won’t be noticeable unless you really push it too fast . . .
I’ve just taken the aircraft up again, checking deflection values on the ground and in the air. They are correct. They deflect exactly as is expected for a Vulcan, they will not move ‘much more’, that’s just how the Vulcan is - 27° up, 12.5° down are the MAXIMUM values, and these decrease as speed increases.
Descending at high speed with the nose down - another big “No” for the Vulcan - it suffers from Mach Tuck and above 0.88M the mach trimmer progressively moves the stick aft to compensate. This can leave you with little to no aft stick available and at this point the only recovery possible is to extend the airbrakes and wait for the mach number to decrease.
When switching views to the Engineer or Navigator position, the Navigator position flickers / flashes. I noticed both showcase view 2 and 3 are the nav position, maybe a bug?
Unable to return to drone view with INS if previously used the nav or engineer position, pressing ins would then go to that position.
Mapping the “set steering” command seems to have no effect on the plane steering button.
Can’t map the AP pitch and roll rockers in the center console.
Heading selection needle (in bomb mode) is not responding to heading inc and down commands, maybe it should?.
Unsure about the TFR height instrument in the left console, the manual only says to set it to the altitude but what function does it accomplish?
The AEO and Navigator’s panels use the Showcase “Fixed Camera” positions, and the drone camera uses the Showcase “Free Camera” position. They both remain available for use in the Vulcan. Pressing the ‘Insert’ key on your keyboard will take you to whatever the last Showcase camera position you had selected (which in the case of the Vulcan may be the AEO or Navigator’s panels). Then once you are in the Showcase camera, pressing the ‘End’ key on your keyboard will toggle between the two types of Showcase camera. We posted a response to a similar question on the Just Flight forums earlier that may be worth a read: Disable camera system? | Just Flight Community
We also updated some of the control assignments after the manual was published pre-release. The updated manual can be found at “…\Community\justflight-aircraft-vulcan\Documents” and that will have all the non-standard control assignments you can assign to your external hardware.
The Terrain Following Radar (TFR) should be covered in the “Low Level Checks” checklist. The gist of it is, turn it on, select your height, set the MFS/TFR switch to TFR, and the flight directors will then provide vertical guidance to keep you at that height.
I’m very happy to read you guys are working in changing the cameras to internal cockpit cameras instead of showcase cameras, that would be a significant improvement in usability!
Thanks for the TFR micro tutorial!
I’ll take a look at the file you mentioned for my bindings.
The auto chute jettison option only controls the jettison of the chute after it has been deployed and the aircraft has slowed. To deploy the chute, either move the chute switches on the centre instrument panel to STREAM (below 140 KIAS) or using the spoiler arm toggle assignment.
Thought I’d go through the tutorial in the manual today rather than the checklists as previously - two hours it took me to get it ready for takeoff. Admittedly, I spent most of that time looking for stuff and wondering if I’d done it right (disclosure: no. Don’t activate the emergency landing gear to check it’s working after two hours of setup).
Also, was trying to work out a problem with the model and camera views, part of the left side of the model ended up clipping the left console and obscuring the tablet on the seat after switching the interior cams. I can post a screenshot if JF are interested, it’s not here as my PC is shut down now.
Still, got there eventually and did the navigation aspect of the tutorial and was joined by another Vulcan for a while. Landing went really well again and it handled really nicely throughout the flight. Just need to trim the startup down to a more realistic timeframe now, was thinking 90 minutes might be achievable in 6 months.
It’s just another example of Xbox users feeling left out.
I can sympathize with them. Thing is, smaller devs can’t afford parallel development teams. They have to prioritize one market over the other. Either way, someone’s going to feel neglected.
I’m having a problem with my recently installed Vulcan. I’m not able to interact with the tablet in any way. I can click on it to bring it up into view but nothing is clickable on the screen. I can click the button on the left bezel to switch screens but can’t go back to the options screen. Everything appears to work in the cockpit and the aircraft but no joy with the tablet at all. I’ve searched high and low for others having this issue but haven’t found anyone else experiencing this. Any help would be appreciated. Wanted to ask here in case I’m missing something simple before I consult JF support. Thanks in advance folks.
Sounds like a WASM compilation error. I’d try uninstalling and reinstalling it first. Not sure though really. Might be worth checking Legacy vs Locked cockpit interaction settings if it does it again.
