Carrer Mode Liveries

[MSFS 2024] Bug Reports Aircraft
,
1

Version: 1.8.14

Frequency: Consistently

Severity: High

Marketplace package name: FSR300E, Sting S4, TL3000

Context: Carreer Mode

Bug description:

It seems career mode only uses 1 single livery from the package not matter what for all missions, which is incredible odd.

I am getting lots of customers complaining why the same livery is always loading for Phenom 300E during career mode, as far as I can see, all the presets and liveries and everything are configured correclty for all the carreer modes.

However, the system always pick the same livery 100% of the time, it never picks any of the other 20 available liveries for phenom.

Same happens to other planes I offer.

Ideally, other liveries should be used for the missions, to give people variations or the very lest then allow them to pick what livery they want when they buy the plane in carreer mode?**

Repro steps:
**
Pick 10 missions for Phenom on carreer mode, not matter what mission it is, you will always see the blue ace livery, always.

Best,
Raul

2

Hello @SimbolFSReborn ,

In livery.cfg have you put the correct Tag in dressing_codes ?

image
image922×1060 83 KB

Here is the link to the documentation :

3

Do we have to?

The specialization is set on the presets and global configuration, therefore all liveries should be available, no?

Why i have to duplicate the specialization on the livery.cfg again? Doing it 20 times, since I have 20 liveries.

What are we missing?

R.

4

So i’ve ask to the team that manage that.
And there are two options :

Option 1
Put the section and the correct tag on each livery.cfg (as the system is set to work like that).

Option 2
Remove the section [Specialization] from everywhere and the random liveries will be enabled.
But for this option, it means that you have no control over which livery is enabled/disabled according to the type of mission

Other information that might be useful: Depending on the career mode you are (employee or freelance), the system that selects the available liveries is not the same.

For the freelancer, it will always be the same (the one bought by the player).
But for the employee mode, it will be part random, as some liveries will not be available depending on the player’s location (desert, forest, jungle, etc)

5

What you mean by this?

The only place I have set the dressing codes is on the presets.

Looking at the forums, I am not the only 3rd party aircraft affected by this, so either we have a bug on the system or the SDK is designed in a way that nobody is understanding leading to lots of users frustrated with only 1 livery available for carreer mode.

FYI, I been told by users this is happening basically to every aircraft on carreer mode.

R.

6

Hello @SimbolFSReborn

What I mean is remove the dressing var in the preset.
Having the dressing var in the preset actually doesn’t work.
But with this option (option 2 : removing all the dressing var), you will lose the ability to choose where or in which context a livery can spawn.

The correct method is to tell each livery in what condition they can spawn.
So you will need to add this section with the correct tag in each livery.cfg:
[Specialization] dressing_codes = “TAG, TAG, TAG”.

The people who have the problem, are they playing as freelancers or employees?

7

@PowerGecko

The documentation states, an empty string will enable the liveries for all careers:

image
image1228×450 57.4 KB

Which is what I have done for all my fleet, and pretty much every single 3rd party developer, instead, what is happening is, only 1 livery is used all the time in career mode.

I am not sure if you guys are understanding the problem here, career mode is working, the presets have the target specialization as per documentation inside the aircraft.cfg example:

targeted_specializations = PRC-PLC
premium=1

All the checks for carreer mode are passing, locally and via marketplace.

The problem is, only one livery is always used in carreer mode, it never gives the users other options from the 20 available, which should work, as stated on the configuration, see the SDK highlith saying, an empty string, should enable it for all, so the expectation is, the system should pick any available livery.

Not sure if the problem is with frelancers, or employers, this is another big issue for us as 3rd party developers, we cannot test carreer mode properly, we should be granted a way to test this in full, by allowing us to buy the plane in career mode, etc, currenlty we cannot, all we can do, is to fire the career tool and test a mission.

I test my missions an always picks the same livery for phenom, ace blue.

Either the SDK documentation is wrong, or the system is wrong, it makes no sense we would have to edit hundreds of livery.cfg files and put the dressing codes there, where an empty string, should just asume, the livery is available for everything, which is the intended scenerario in most cases.

Preset, aircraft.cfg example:

[MODULAR_MERGE]
auto = true

[FLTSIM.0]
title = "FSReborn Phenom 300E Manchester Interior" 
ui_variation = "Manchester Interior"
ui_powerplant_specifics = "Pratt & Whitney PW535E1"
ui_instrumentation = "Garmin 3000"
ui_additional_information = "The aircraft boasts a spacious and comfortable cabin with features like large windows, comfortable seating, and a private lavatory."
isUserSelectable = 1
capacity = 8
targeted_specializations =  PRC-PLC
premium=1

This is an example of a livery.cfg:

[Version]
major = 1
minor = 0

[General]
Name = "FSReborn Delta Charlie"

[Selection]
required_tags = ""

[Specialization]
dressing_codes = ""

[Panel_DynamicParameters]
param.0="color,White"
param.1="stroke_size,0"
param.2="stroke_color,black"
param.3="font_scale,1"

Since the dressing codes is empty, I am expecting this livery to be available for all career modes enabled, all liveries are configured like that, so why then only 1 livery is always used? it should be any livery.

Best,
Raul

8

@PowerGecko

I asked users on my forums topic, he answered very clear what’s going on:

Great feedback for you and your team to understand better the underlying issues.

Best,

Raul

1 Like
9

Hello @SimbolFSReborn ,

Thanks for the response, I correctly understand the problem.
Also, I checked the feedback on your forum; I will report it.

On my side using the DA62 and having the same config seems to work.

Could you please send us the package?
(Using point number 3 of this topic How to report a bug or crash )

10

Just sent it to the private group as per instructions @PowerGecko

Thanks,

Raul

1 Like
11

Hello @SimbolFSReborn ,

On my side, the system works (sorry for the poor video quality, the limit is 15mb) :


Maybe there is a step that I’m missing?

12

I am sharing this with customers, to see if they guide us and explain.

The post that zadma did, implies, they never get to chose a livery when they buy the plane in Freelancer mode, and only 1 livery is forced on them.

What mode you using?

R.

13

I use employee mode.
I’m not sure why, but in freelance I’m blocked at the insurance step (I can’t choose one).
I’m working on it to see why, and after that, I will try it as a freelancer.

1 Like
14

Any news on this?

R.

15

Hello @SimbolFSReborn,

I was off the last few days (sick).
I will continue the investigation, sorry for the delay.

1 Like
16

Hey @SimbolFSReborn ,

So I’ve created the bug for the freelance part where it is impossible to choose a livery.
But I still can’t reproduce the problem in the employee mode (where it is always the same livery).

17

Thanks you so much, this will be a very good thing to implement for everyone, people really want that :sparkling_heart: .

Did you try to repaint the plane in employee mode, like on the link they posted? just to be sure we covering the entire feedback from the users.

Best,
Raul