[MSFS2024] Boeing C-17 Globemaster III

I think not, because the co-pilot seems to be more or less a normal size, while his surrounding, chair, yokes etc. is huge to his size. In VR you measure better all haha, VR users are more fussy picky in that.

Noted, I think I know the reason behind.

This is very much related to high latitude and the pink line issue you reported. Looking into it.

1 Like

Managed to land at south pole, looks like Asobo fixed the polar performance/nav issues, really happy to see that.

The HUD altitude actually corrected itself as I got even closer to the pole.

The only other bug I’ve noticed is within about 10NM of the pole the ND was doing a weird glitch:

Liking the aircraft a lot, thank you.

I really like the idea of you guys being on this post and giving updates/ comments here!

9 Likes

Thread with the largest number of views and replies in the msfs-2024 Polls and Feedback section
 I enjoy being around the forums :wink: (and ultimately getting feedback! Every single post is logged and tracked)

14 Likes

Hello there, nice work on that beautiful bird :wink:

As others mentioned it feels a bit heavy on my system too even after caching in direct comparison to other aircraft like the iniBuild ones. Maybe there can be something done by optimization (could be tied to some LOD configuration things or be improved by a different DDS compression method)

However another thing I notice is that the aircraft atc information seems not working correctly. If it’s still partly the same default localization file Asobo uses as in MSFS (2020) you could use the following lines instead:

atc_type = "TT:ATCCOM.ATC_NAME BOEING.0.text"
atc_model = "TT:ATCCOM.AC_MODEL C17.0.text"

for icao information it would be that as per standards (if you don’t already have these in place)

icao_type_designator = "C17"
icao_manufacturer = "BOEING"
icao_model = "C-17 Globemaster 3"
icao_engine_type = "Jet"
icao_engine_count = 4
icao_WTC = "H"

icao_model = “C-17 Globemaster 3” can also be "CC-177 Globemaster 3" as per Aircraft Type Designators

Cheers!

Nothing to do with art - It’s the HTML gauges having a massive impact on FS24 vs FS20!

Its a core sim problem + enhanced by the fact that the C17 has a total of 35 individually modeled displays. Other aircraft (eg. Inibuilds) use WASM so its completely unaffected by this issue: Coherent has a MASSIVE performance impact on FS24 - #5 by B21 - HTML/JS - MSFS DevSupport

A workaround: Set your Glass Cockpit Refresh Rate to low or medium. You will see a massive performance boost.

Noted and fixed

2 Likes

Perfect, thank you for pointing out :slight_smile: looking forward to see stuff getting improved by time :wink:

That was fast :wink: incredible! Keep up that pace (but not at all personal cost :wink: )

2 Likes

Congrats on a well done aircraft, this has been a bright spot for me in an otherwise frustrating MSFS2024 release. Thanks as well for being present here in the forums.

One thing I noticed was I tried to use the callsign Bison but there seems to be something overriding it as ATC call me RCAF instead. This was the grey tail RCAF repaint.

Thanks,

Dave

3 Likes

This seems to be a pretty fun simulation!

Is there an option to get the flight path marker to work? The panel option for the ghost flight path marker didn’t seem to separate the vertical and horizontal components of the flight path marker either.

Am I missing an option to get it working?

I tried to do a flight yesterday and struggled on 2 points. I did read the manual but could not see anything saying how to add cargo and fuel. I’d assumed the EFB would be it, but I don’t see any response when clicking or dragging on the fuel page. Decided to ignore as there was fuel in the tanks, set up a flight plan and yolo’d. Yolo’d straight into the trees because the plane would not lift off
 Stick was moving but no pitch into the sim. Sure I missed something


I will watch the tutorial videos shortly and hopefully all is revealed.

One other major thing for me I use Spad and while struggling through the setup of altitude I found that I could turn the dial and it would display correctly in feet on the FCU but internally it looked to me as if the value is in meters? I think 100ft was displayed as 34.nn which I guess would be meters. I trawled all the variables available and none would match the FCU value.

So - specific request(s):

  1. Please tell me which var holds the target alt in feet
  2. For real bonus points (and I wish every dev team would) could you please share a list of relevant lvars and events

It seems like every plane (including from the same dev) uses a different scheme - some inputs driven by lvar value and some by events.

Personally, so far, the champs have been tfdi with the MD11 who use input events to drive all the controls but what’s really great is that they provided a complete list of every input possible and which parameter to use. This is the way :slight_smile:

If you change callsigns it shouldn’t get overwritten
 I’ll check on my end. Perhaps a sim issue!

We in fact had to temporarily disable it before launch as it wasn’t working well on FS24 (worked fine on FS20). That bit of code needs some reworking, and its noted for review.

This is a “dual EFB” aircraft - you have the aircraft Loadmaster EFB (located on the left of the pilot seat, and in the Loadmaster station). From there you can load predefined cargo objects into the cargo bay by selecting them on the Payloads tab.

For specific cargo amounts, and fuel, you must use the MSFS EFB, which you can access by pressing Tab on your keyboard. Then click on the aircraft icon, and Fuel&Cargo

Very likely your Hyd pumps are off, make sure all 12 of them are on in the overhead panel (3 pumps per engine). No Hyd pressure, no control surface movement.

The easiest way is to read the corresponding AVARs for autopilot (A:AUTOPILOT ALTITUDE LOCK VAR) , Make sure to read this variable in Ft as MSFS will automatically convert to any units you request.

My recommendation is always to use B events. All the knobs, switches and buttons have corresponding B events associated that can be programmed into hardware using SPAD. I should create a guide on how to find and use B events as there is very limited info online.

Edit: In fact this video is very handy: https://www.youtube-nocookie.com/embed/QKlOUs-xtns B events exist for anything interactable on any cockpit in the simulator

4 Likes

Same issue here on xsx - extreme low fps, not usable as is.

as addressed above - known issue, related to a core FS24 bug: [MSFS2024] Boeing C-17 Globemaster III - #54 by LikedHare478430

Thanks - I do try to use B: events whenever I can, a list would be great as it would save huge amounts of time.

Hello, wanted to confirm the callsign issue was a mistake on my end, I was trying to set a callsign in the EFB flightplan section. All good now that I’m entering the callsign in the right place :slight_smile:

2 Likes

Update 1 Officially sent to Microsoft - don’t have an ETA at this time as the team is out for Thanksgiving break.

UPDATE 1 - (v1.0.5)

  • FIXED: Contrast and weathering on all liveries, improved throughout.
  • FIXED: Main Landing Gear sinking on the ground on heavy loads.
  • FIXED: Added additional weathering to cockpit textures.
  • FIXED: Rivets white outline when viewed from afar.
  • FIXED: Improved Engine Cowling texture
  • FIXED: Primer Livery registration incorrect.
  • FIXED: Ground Spoiler ARM Knob, corrected the Tooltips
  • FIXED: Increased resolution on Tablet EFB Textures
  • FIXED: Maximum fuel load in Lbs displaying incorrectly due to wrong fuel type on Flight Model
  • FIXED: When spawning on the runway, stab trim is configured for takeoff.
  • FIXED: ATC designation fixed.
  • FIXED: Incorrect naming order in aircraft resolved (manufacturer name missing)
  • FIXED: COMM/SKE Tooltips corrected
  • FIXED: Issues on the engine geometry
  • FIXED: Other minor tooltip edits
  • FIXED: ATC Callsigns overwritten for some liveries.
  • FIXED: Stab Trim alarm adjusted
  • FIXED: RA/BA was inverted on the HUDs
  • FIXED: Course variables completely disconnected from varios Navigation Display screens
  • FIXED: ETA to destination at low speeds calculation improved
  • FIXED: Transponder on ND now displaying correctly mode
  • FIXED: Overspeed alarm triggering at 250kts under 8000ft
  • FIXED: Yaw damper not engaging with autopilot when using keybinds/hardware binds
  • FIXED: Aircraft nose disappearing on Walkaround mode.
  • FIXED: Various LOD issues
  • FIXED: Engine blast effects detached fixed
  • ADDED: Multilanguage LOC Translations added
  • ADDED: Added “Documentation” page to EFB, with links direct to the Aircraft Manual
  • ADDED: Walkaround items improved - Engine Covers can now be removed from walkaround, added tire pressure checks. Added preflight walkaround to Checklist
  • ADDED: Additional conditions for a successful engine start added - Engines will fail to start if PRI or SEC Hyd Pumps are on, fail to start if APU Bleed is off.
  • ADDED: APU can be started without fuel pumps (gravity feed), but will be fuel deprived after two minutes if boost pumps are off.
  • ADDED: Engine Ignition will auto-switch off when N2 greater than 52%
  • ADDED: Added APU to allow feeding from Fuel manifold
  • ADDED: Fuel transfer among tanks is now possible using the FILL and XFER valves/pumps
  • ADDED: Engine crossfeed is now possible. NOTE: Crossfeeding and fuel transfer is not possible at the same time.
  • ADDED: Fuel Dump is now possible
  • MISC: Cargo Bay flag temporarily disabled, being moved and reanimated.

PUSHED TO NEXT UPDATE

  • EFB to FMC (and viceversa) Flightplan Sync - Work in Progress
  • Contrails “Detaching” from engines, displaying as single contrail - Waiting for Asobo Fix, LOD issue
  • Internal sounds “detaching” after change of cameras - Waiting for Asobo Fix, LOD issue
  • Performance drops due to Coherent avionics module, primarily on Xbox and Low-End PCs - Core Sim issue, Asobo identified the issue, waiting for update.
  • Along with other smaller bugfixes and new features
16 Likes

I can’t seem to hear the default ATC though I can talk to them, usually that’s a radio volume issue but according to the manual the volume panels don’t function? Any thoughts on how I can hear ATC? Thanks

Have you removed the headset from the glareshield? You won’t be able to hear ATC until you wear them :wink:

Or is this happening when starting from Runway?
EDIT: I see the issue, will push a fix with Update 1

2 Likes

The discord link links to Facebook