
Messttr
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by Messttr
-
-
The display type is not recognised and followed according to liveryconfig.cfg even though it was included as fixed in 1.0.5 changelog. Photo below from 1.0.7 with fresh install (you can see according to config file it should be new the type of display). This is a pending bug I have already reported, but it has not been fixed.
-
The display type is still not recognised and followed according to liveryconfig.cfg even though it was included as fixed in 1.0.5. Photo below from 1.0.7 with fresh install (you can see according to config file it should be new the type of display). @haza2
-
33 minutes ago, sunake said:
Naah. I like it the way it is.Â
 It makes no sence to fly eg. Delta aircraft in Kgs 😂 it would be much better to have it linked to the liveryconfig file... also it would be nice to have the option in OIS to override the options locked by the file.
-
1
-
1
-
-
Both toilet doors in the rear galley are opening in the wrong direction. 😄
-
After the 1.0.1 update, the display type appears reversed compared to the value set in the LiveryConfig.cfg file under the INI_OPTION_DISPLAY_OLD setting. Specifically, INI_OPTION_DISPLAY_OLD = 0 should correspond to the new display type, and INI_OPTION_DISPLAY_OLD = 1 should correspond to the old type. However, following the update, every livery based on earlier airframes loads with the "new" display type, and vice versa. The image below shows the F-HTYA by iniBuilds, which is correctly configured in the cfg to have the new display type, but is now incorrectly displaying the old type.
-
The weight units (lbs/kgs) used by the specific airframe should depend on the liveryconfig.cfg file, so that when you load, for example, Delta Air Lines A350, the aircraft loads with the correct weight units, lbs, and for example when you load Finnair A350, it loads in kgs.
-
2
-
Display type option not being honored when specified by airframe after 1.0.5 update
in Systems
Posted
Hello, after update 1.0.9 the issue still persists. It is a little bit annoying now. 😕