Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

That "-1" in "fuselage_length" on some aircraft...

Featured Replies

Since I got my hands on MFS I couldn't resist "exploring" it's ".CFG" files, following the work of many modders contributing to make them more realistic / plausible according to data on their RW counterparts and trying to glimpse what's new in the "Modern" FDM...

One of the things stumped me when looking into some of the "flight_model.cfg" files, like those of the Extra 300 and the C172 was a value of "-1" set as fuselage_length ???

Indeed, if you open those files you'll find:

fuselage_length = -1

Setting this value to realistic real world data certainly makes a difference in the flight dynamics, and laying with any values away from it, in this and other parameters in that same file, like for instance "fuselage_width" does make a difference, and can actually be easily observed in the size of that orange cylinder that represents the fuselage in the Modern flight model and can be visualized, together with other shapes used for the wings, engine(s), landing gear(s), etc... when we enable "Dev Mode" in the sim.

But I really wonder why some aircraft have this "-1" for their length ?

Any ideas ?

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

It's fairly common (though certainly not "good programming practice") to use an invalid value in a parameter as a flag of some sort, generally an indication not to use that value.  My guess - and this is certainly nothing more - is that this disables certain calculations related to the fuselage length, possibly replacing them with stability derivatives from the legacy flight model.  May be a useful debugging tool, either left there by mistake or because the more complex calculations aren't giving the right result. 

  • Author

Thx @lzamm

Very plausible hypothesis !

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

11 hours ago, jcomm said:

Setting this value to realistic real world data

Silly question: What would that realistic data be? Meter, Feet, CM? I'd like to try the above but have no clue what to insert.

Best regards

Edited by ThomseN_inc
Found it! :P

Intel i9-13900K | Gigabyte Z790 Aorus Master | RTX4090 | 2x16GB Corsair Vengeance DDR5-6000 | Be quiet! Pure Loop 2 FX AiO | Win 11

  • Author
3 minutes ago, ThomseN_inc said:

Silly question: What would that realistic data be? Meter, Feet, CM? I'd like to try the above but have no clue what to insert.

Best regards

It's in feet for the corresponding flight_model.cfg entry.

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

I've done some of my own poking and I've found that not all parameters are used by the flight model engine. This may be one of those (so someone at Asobo decided to set it to -1 since it was unused). It would not surprise me if unused parameters are there for: legacy reasons; future consideration; 3rd party use.

[email protected] - ROG Strix Z790-E - 2X16Gb G.Skill Trident DDR5 6400 CL32 - MSI RTX 4090 Suprim X - WD SN850X 2 TB M.2 - XPG S70 Blade 2 TB M.2 - MSI A1000G PCIE5 1000 W 80+ Gold PSU - Liam Li 011 Dynamic Razer case - 58" Panasonic TC-58AX800U 4K - Pico 4 VR  HMD - WinWing HOTAS Orion2 MAX - ProFlight Pedals - TrackIR 5 - W11 Pro (Passmark:12574, CPU:63110-Single:4785, GPU:50688)

  • Author

Well, I did play with it and it certainly made a diffference, as well as, for instance, fuselage_diameter and fuselage_center_pos...

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.