G3000 V2 Avionics, behavior files are failing to load

[MSFS 2024] Bug Reports Aircraft
, , ,
1

Version: 1.5.4.0

Frequency: Consistently

Severity: Blocker

**Marketplace package name:**NA

Context: What package? any package in devmode

Bug description:
Unable to load Working title model behaviors for G3000V2

Not matter what I do, it never finds the behaviors files, something is fundamentally wrong here, I am about to give up, been trying this days guys, it cannot be this hard to just invoke the G3000 behaviors file into my cockpit?.

Repro steps:
Just put this in the definition:

<Behaviors version="1">
		<Include ModelBehaviorFile="Asobo\Common.xml"/>
		<Include ModelBehaviorFile="Asobo\Generic.xml"/>
		<Include ModelBehaviorFile="WorkingTitle\GlassCockpit\G3000v2\BehaviorsV1\G3000.xml"/>

		<Component ID="AS3000">
			<UseTemplate Name="WT_G3000_PFD_Template">
				<ID>1</ID>
			</UseTemplate>
			<UseTemplate Name="WT_G3000_PFD_Template">
				<ID>2</ID>
			</UseTemplate>
			
			<UseTemplate Name="WT_G3000_MFD_Template">
			</UseTemplate>
		</Component>
	
</Behaviors>

It result with errors in the console:

image
image1839×312 56.8 KB

Obviusly the SDK is installed correctly:

image
image1470×400 39.2 KB

And uppon inspection on the VFSprojector, the definition where these are stored by the VFS projector seems different, I also noticed the two airplanes that uses the G3000 (TBM and SF50) they copied the G3000 behaviors locally? and then reference them locally by using include relative model files inside their own package?

Surely that cannot be right? if then in a next SDK / patch comes, and those behaviors have fixes, the airplanes would not receieve them unless you re-copy things to recompile?

FEEDBAK

Discovering how to set up each of the new avionics in MSFS 2024 is incredible difficult to work out, and it shouldn’t be this hard to put some avionics behaviors into an aircraft, I consider myself an advanced developer after having delivered 3 airplanes in MSFS 2020, 2 of them considered one of the best in the market on their class, and yet here I am 3 days trying to put G3000 avionics for my product unsucessfully.

1st problem: Screen textures requires emission factors as minimun as 3500, nothing in the documentation explain this, failing to set emission factors on the material results on avionics being black all the time, I managed to inspeac a GTLF file of the TBM via the inspector to learn this the hard way, this should not be the case.. any new developer coming into the space, would just give up thinking is too hard to do this, specially freeware devs,

2nd problem: Model behaviors as reported here, still stuck unable to make them work.. looks like I have to copy then locally to get going, but surely, this is not the right way to do things?

Any help on this would be greatly apreciated.

Best,
Raul

1 Like
2

Update

I copied the WT G3000V2 behaviours locally on my package, just like the SF50 an TBM900 is being done, and then I referenced the behaviours via a relative model behaviour file, this loaded them and allow me to work in the meantime.

However, I been discussing this with Working Title and they agree something is wrong, just using this:

<Include ModelBehaviorFile="WorkingTitle\GlassCockpit\G3000v2\BehaviorsV1\G3000.xml"/>

Should work, and we should try to avoid having the need to copy them locally, which is clearly a disadvantage since it would not allow to get SDK updates automatically.

In any case, wanted to let the team know what I did to keep moving while this can be investigated in the future.

Best,
Raul

3

I believe you are mistakenly thinking that the SDK folder is the link, while it should be the actual VFS file structure.

Note the difference in the SDK folder structure compared to the actual MSFS package folders

\Microsoft Flight Simulator 2024\Content\Packages\workingtitle-instruments-g3000-v2\ModelBehaviorDefs\WT\G3000v2\BehaviorsV1

F:\MSFS 2024 SDK\ModelBehaviorDefs\WorkingTitle\GlassCockpit\G3000v2\BehaviorsV1

DA40CGDFQ_2025.06.04_9h47m55s
DA40CGDFQ_2025.06.04_9h47m55s1531×929 51.9 KB

Also note the file size differences and the date differences. (but comparing them they are the same).

4

Nope, I tried this too Ron (I tried everything, and WT was helping me on this advising what to put, the one I posted initially is advised by them, they agreed it should work), and what happens is, then you get another error on the console where it complains it cannot read c:\MSFS 2024 SDK\ModelBehaviorDefs\ WT \G3000v2\BehaviorsV1 for processing.

And this is what I think is the problem, the VFS is mounting the behaviors in a different folder structure as the SDK, the installed SDK is ModelBehaviorDefs\ WorkingTitle\GlassCockpit\G3000v2 \BehaviorsV1

Where the VFS is ModelBehaviorDefs\ WT\G3000v2 \BehaviorsV1

The discrepancy must be causing all this mess, so far all the planes using G3000V2 in the base package have them copied manually, so, on the current public flighting and public non flighting of MSFS 2024, referencing these directly, is not working.

Asobo needs to look at this and correct it..

R.

5

It actually looks at the SDK folder? That makes no sense. Hope ASOBO at least gives us a reviewing it message. This would be a core functionality that would affect all devs.

6

Yes, because in 2024 the behaviors can be compiled and thus must be resolved at compile time, not from the VFS, in the compiled behaviors case. The docs call out this requirement on this page: Model Behaviors

Screenshot_20250604-110543
Screenshot_20250604-1105431080×1165 138 KB

Thanks,
Matt

1 Like
7

Yep, and the Asobo_EX1 are working fine.. is the WorkingTitle ones that are giving errors.. very odd.

Thanks for coming to help us on this matter, and also to your team last night on discord who was trying to get me going..

Best,
Raul

8

Thanks, my bad. See how easy it is to make addons for 2024?

Guess we’ll wait for SDK 1.4.2

1 Like
9

Weekly bump..

1 Like
10

Hello @SimbolFSReborn

I think the problem here is that you are not using compiled behaviors, but the path you provide is the one for the SDK G300v2 template.

Instead, for non compiled behaviors, you want to use the VFS path, which in this case is different.
I think the path you are looking for is WT\G3000v2\BehaviorsV1\G3000.xml

Regards,
Sylvain

11

If I use that path, it doesn’t work either because the console complains it cannot find that path to read them.. I did try that too..

This only worked when I copied then manually, just like TBM and all other G3000 type of avionics planes are doing..

R.

1 Like
12

At least, with the snippet you provided in your repro steps, that’s enough to solve the Include : Can't find file error.
Now there can be more.
Note that if you are providing a wrong path to a compiled behavior, the error is slightly different and will look like: ModelBehaviorsLister | ModelBehaviorDefs file does not exist: <path>. Is the SDK installed?

I can’t tell what’s wrong without having more information about your project or the errors it produces.

Regards,
Sylvain

1 Like
13

Hi Sylvain @FlyingRaccoon,

I am on my way to FSExpo, give me time to get back and I will submit privately a project for you to test.

Thanks for looking into this.

Raul

2 Likes