MSFS Products

Very cool, I'll need to see if I can find the right weather conditions. Exciting to hear that there are new features coming in the future. Keep up the great work! Sometimes I stream the RJ here Deephack Plays My main channel is here although it's more DCS focussed Deephack

Hello BlackSquare, The first one is just a feature request which has disappeared due to time. It is to simulate proper feathered propeller motion on the props instead of the disc like motion currently displayed when feathered. I have read from another user that turboprops on other aircraft by BS already have this. Although already mentioned, the registration plates were working absolutely fine up to MSFS 2024 SU3 Beta 1.5.9.0. But after the .10 fiasco over FSExpo and subsequent builds, the plates broke. Any update on getting these back? The third is a bit more complex. It is regarding indicated vs. actual fuel flow. I noticed this on my flights and comparing table fuel flow vs. indicated. I am referencing the values on the Maximum Range Power Tables from a Beech 2000 POH on a personal website that has excellent Starship documentation. I was indicating a fuel flow value much lower, however on my OFP, I was not gaining fuel. For the test, I have set a 1-hour timer and noted the fuel value at start and at the end. I was cruising at FL370 and ISA was at +4°C. So, I extrapolated between the ISA and ISA+10°C tables. But that is not the point. The point is the difference between indicated and actual. Barring you from the minutiae of a ton of observation values, I have taken calculated fuel flow at time stamps 15 min., 30 min. and 60 min.. I have taken the average of that. The result is, in this hour: Indicated fuel flow dropped from 210 to 203 pph per engine. Calculated fuel flow also dropped a bit across the 60 minutes. Taken the average of three time stamps, I conclude, Average Indicated fuel flow is 206 pph per engine. Average calculated fuel flow is 228 pph per engine. Conclusion, the panel fuel flow indicator should be (228-206=22 / 22/206*100=10.7%) 10.7% higher to match what the engine is really consuming. Lastly, let me just say what an ABSOLUTE dream this thing is. After all the planning is complete, you depart in twilight and the lighting as absolutely amazing! From the blue area lighting to the red RTU LED's .... absolutely delightful and satisfying. A HUGE thank you as well for the SimBrief takeoff and landing performance. I doublechecked it with the AFM and it is just SPOT on !!! Cheers, Xander a.k.a. 777Drvr

@miked176766 I think I have found the problem. I purchased the PA38 Tomahawk on the MSFS 2020 Marketplace and this updated in MSFS 2020 on Friday (20/06/25). This worked fine in MSFS 2020. I ran MSFS 2024 and looked in my Library for the PA38 Tomahawk which still shows as the 2020 version not certified for MSFS 2024. I set this version to install and stream. On running the aircraft it loaded and allowed me to enter the cockpit. I tested for full control movement stick and rudder which both showed full movement. On starting the engine I could only get aileron movement, no elevator or rudder. With this version still set to stream the loss of elevator and rudder is passed on to the PA28’s that are installed as MS 2024 certified. If I then set the PA 38 to disabled the PA 28’s all return to normal rudder and aileron behaviour. My conclusion is that until we have an MSFS 2024 certified copy of the PA38 Tomahawk in the marketplace this problem will persist.

In v0.1.3 of the Vulcan, we upgraded the GPS from the Aera GPS to the G3X Touch for better MSFS 2024 compatibility. Therefore, the functionality of the GPS has changed slightly as the G3X Touch is a more advanced GPS. To cover each of your points: If a flight plan is created in the MSFS 2024 EFB, the "Send Route To Avionics" button must be pressed in order to import the route into the GPS. If a flight plan is created manually within the GPS, the flight plan must have a departure airport and a destination airport set in order for the autopilot to couple with the GPS (if a flight plan is created in the GPS with only a departure airport and waypoints, the route will be displayed, but the autopilot coupling will not function with an incomplete flight plan). In order for the autopilot to track the GPS flight plan, the ENGAGE knob must be pulled (with IN indicator showing white), the TRACK knob must be pulled, and REMOTE must be selected on the navigational selector. This is a known side effect of a workaround we have put in place to improve touchscreen display interactions in our aircraft in MSFS 2024. If the workaround is no longer required after future MSFS 2024 Sim Updates, we will update the logic so that control cannot be clicked through touchscreen displays. The GPS can also be moved on top of the glareshield by clicking the upper bezel. As the G3X Touch is a default GPS unit in MSFS 2024 (developed by Working Title), we sadly don't have any control over the scaling of the GPS. To circumvent this, we have added custom cameras for each GPS position which moves the camera closer to the GPS display. These cameras can be toggled either via the MSFS Camera menu, or via a clickspot on the right bezel of the GPS. Mark - Just Flight

"site not found"

We're aiming to finish work on the 146 upgrade and MSFS 2024 compatibility in July.

Hi, I spent some time chatting with the FSHud developer today and we were able to work out what the problem was here. FSHud should be compatible with FS Traffic once the sim settings have been configured correctly according to the quick start guide in the FS Traffic manual. The FSHud admin has posted a clarification on their Discord: [image: 71ffa6b3-5262-44c0-938f-010b33595cad.png] Thanks for reporting the problem, and thanks to the FSHud admin for their time.

The throttle axis snapping between IDLE and 100% is likely the result of the control conflict. Do you perhaps have any controls assigned to "TOGGLE ENGINE 1 FUEL VALVE" or "SET ENGINE 1 FUEL VALVE"? Those assignments are used to move the throttle lever between the HP OFF and IDLE positions, so they could be 'fighting' against the throttle axis position. Mark - Just Flight

Hi. Sorry if this has already been answered. But juring normal flight, ( I expect this on take-off) I have to constantly steer to the right. I don't remember this happening in 2020, but in 2024 I have this problem. I am using version 0.4.3. any help please

The real-world aircraft does have a difference in elevator deflection angles on each side of neutral (+16 degrees and -8 degrees off the top of my head), so it is expected behaviour to see the difference in movement range. However, from my discussions with our flight model developer, the difference in elevator deflection angle on either side of neutral is something MSFS doesn't handle all too well, so the small deflection angle is necessary in order to preserve the handling qualities of the aircraft. Essentially, even with that small deflection angle that you are seeing in the latest build, the aircraft should have a similar level of effectiveness as if it had the larger deflection angle. Hope that helps. Mark - Just Flight