Why all these Dev Console errors (even after 5 Updates )?

Why all these Dev Console errors (even after 5 Updates ) ??

What was the Point of the Dev Console, if not to display errors, and what is causing them, so they are easily fixed.

NONE of the ERRORS below are difficult for Asobo to fix … so why, after 5 updates, are we still seeing them, “embarrassingly” displayed in the Dev Console ???

Come on Asobo, this does not instill any confidence in your QC or testing processes !!!

And, this is just with the C172 loaded. (and Ground vehicles)

I suspect other SimObjects have their own mass of ERRORS ?

Model behaviors XML
File: ASO_Aircraft_Caddy.xml
Model verification
No matching animation “Gyrolight”.
ID: LIGHTS
Node:
Animation: Gyrolight
PartIds:

Model behaviors XML
File: ASO_Aircraft_Caddy.xml
Model verification
No matching animation “Wheel_Orientation”.
ID: WHEELS
Node:
Animation: Wheel_Rotation, Wheel_Rotation
PartIds:

Model behaviors XML
File: ASO_Aircraft_Caddy.xml
Model verification
No matching animation “Wheel_Rotation”.
ID: WHEELS
Node:
Animation: Wheel_Rotation
PartIds:

Model behaviors XML
File: ASO_Aircraft_Caddy.xml
Model verification
No matching animation “Locker”.
ID: PUSHBACK
Node:
Animation: Locker
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “LIGHTING_Knob_Panel”.
ID: LIGHTING_KNOB_PANEL
Node: LIGHTING_KNOB_PANEL
Animation: LIGHTING_Knob_Panel
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_Localizer_2”.
ID: INSTRUMENT_CDI_2_2
Node:
Animation: INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_Glide_2”.
ID: INSTRUMENT_CDI_2_2
Node:
Animation: INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_From_2”.
ID: INSTRUMENT_CDI_2_2
Node:
Animation: INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_To_2”.
ID: INSTRUMENT_CDI_2_2
Node:
Animation: INSTRUMENT_CDI_Compass_2, INSTRUMENT_CDI_Compass_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Compass_2”.
ID: INSTRUMENT_CDI_2_2
Node:
Animation: INSTRUMENT_CDI_Compass_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Needle_Localizer_2”.
ID: CDI_LOC_GLIDE_NEEDLES_2
Node:
Animation: INSTRUMENT_CDI_Needle_Glide_2, INSTRUMENT_CDI_Needle_Glide_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Needle_Glide_2”.
ID: CDI_LOC_GLIDE_NEEDLES_2
Node:
Animation: INSTRUMENT_CDI_Needle_Glide_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Knob_Course_2”.
ID: INSTRUMENT_CDI_KNOB_COURSE_2
Node: INSTRUMENT_CDI_KNOB_COURSE_2
Animation: INSTRUMENT_CDI_Knob_Course_2
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_Localizer_1”.
ID: INSTRUMENT_CDI_1_1
Node:
Animation: INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_Glide_1”.
ID: INSTRUMENT_CDI_1_1
Node:
Animation: INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_From_1”.
ID: INSTRUMENT_CDI_1_1
Node:
Animation: INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Flag_To_1”.
ID: INSTRUMENT_CDI_1_1
Node:
Animation: INSTRUMENT_CDI_Compass_1, INSTRUMENT_CDI_Compass_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Compass_1”.
ID: INSTRUMENT_CDI_1_1
Node:
Animation: INSTRUMENT_CDI_Compass_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Needle_Localizer_1”.
ID: CDI_LOC_GLIDE_NEEDLES_1
Node:
Animation: INSTRUMENT_CDI_Needle_Glide_1, INSTRUMENT_CDI_Needle_Glide_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Needle_Glide_1”.
ID: CDI_LOC_GLIDE_NEEDLES_1
Node:
Animation: INSTRUMENT_CDI_Needle_Glide_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_CDI_Knob_Course_1”.
ID: INSTRUMENT_CDI_KNOB_COURSE_1
Node: INSTRUMENT_CDI_KNOB_COURSE_1
Animation: INSTRUMENT_CDI_Knob_Course_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_Needle_Engine_RPM_1”.
ID: INSTRUMENT_NEEDLE_ENGINE_RPM_11
Node: INSTRUMENT_NEEDLE_ENGINE_RPM_1
Animation: INSTRUMENT_Needle_Engine_RPM_1
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_Knob_Clock”.
ID: INSTRUMENT_KNOB_CLOCK_1
Node: INSTRUMENT_KNOB_CLOCK
Animation: INSTRUMENT_Knob_Clock_Push, INSTRUMENT_Knob_Clock_Push
PartIds:

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_ADF_Knob_1”.
ID: INSTRUMENT_ADF_KNOB_1
Node: INSTRUMENT_ADF_KNOB_1
Animation: INSTRUMENT_ADF_Knob_1
PartIds: INSTRUMENT_ADF, INSTRUMENT_ADF1

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_ADF_Needle_1”.
ID: INSTRUMENT_ADF_NEEDLE_1
Node: INSTRUMENT_ADF_NEEDLE_1
Animation: INSTRUMENT_ADF_Needle_1
PartIds: INSTRUMENT_ADF, INSTRUMENT_ADF1

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “INSTRUMENT_ADF_Dial_1”.
ID: INSTRUMENT_ADF_DIAL_1
Node: INSTRUMENT_ADF_DIAL_1
Animation: INSTRUMENT_ADF_Dial_1
PartIds: INSTRUMENT_ADF, INSTRUMENT_ADF1

Model behaviors XML
File: Cessna152_interior.xml
Model verification
No matching animation “FUEL_Lever_Mixture_1_Push”.
ID: FUEL_LEVER_MIXTURE_1
Node: FUEL_LEVER_MIXTURE_1
Animation: FUEL_Lever_Mixture_1_Push, FUEL_Lever_Mixture_1_Push
PartIds: FUEL_MIXTURE, FUEL_MIXTURE1

Model behaviors XML
File: ASO_Baggage_Cart01.xml
Model verification
No matching animation “Link”.
ID: LINK
Node:
Animation: Link
PartIds:
Model behaviors XML

File: ASO_Baggage_Cart01.xml
Model verification
No matching animation “Wheel_Rotation”.
ID: WHEELS
Node:
Animation: Wheel_Rotation
PartIds:

a) maybe you should them interpret as warnings
b) maybe these show up because the aircrafts are not finished and these things are not yet implemented
c) plz stop with ‘easy fix’ etc. as long as you are not a software developer AND know asobos code.

3 Likes

Well,
a) I am still a software developer (and was for a Major International Aerospace Company)
b) the errors come from code that is exposed to the user, so yes, I do “know” that code. - I looked
c) They are EASY Fixes

And who are you to tell me to stop expressing my opinion in this public forum ??

7 Likes

Well you’re answer shows that you obviously have no idea about software developing.
Just because you see an error code does not mean you know their code.

Maybe they don’t need fix as the aircraft don’t have these animtations/systems.

I’m out now…

2 Likes

Thank you for your invaluable contribution to this thread … bye …

Deadline: Get Xbox version ready by ***** (date)
Deadline: Get new code implemented and tested for SDK updates
Deadline: Get a million other things done by yesterday.

Plonker on forums. Why haven’t they fixed these minor error messages.

Erm? Because they have more important things to do?

Game development is orders of magnitude more complex and time consuming than you obviously imagine. And yes. I am a game developer. Sure someone could spend a day going through all of those issues you have listed but that’s a day they didn’t spend doing something more important that would have a bigger impact on the game.

Oh and once they ‘fix’ all those error messages, they need to spend more time to test that it all works as expected now, and then fix the new bugs that unexpectedly appeared due to the changes.

Or they could put it on the back burner until more important stuff is done.

1 Like

I stopped taking you reply seriously at “Plonker” !!!

Do you even know what a “Plonker” is ? (sigh)

Noun. plonker (plural plonkers ) (Britain, slang, mildly derogatory) A fool. (Britain, slang)

2 Likes

LOL so you had to look it up !!!

Good job you did not post the other meanings you most obliviously saw when you looked it up, in this forum. That would have been a STRIKE !!!

"Thank’s mate for that - or I might have been “Scotch Mist”

1 Like

@Beginner314 Speaking from experience I would also judge these errors as easy fixes. And if these errors are harmless I would certainly don’t show them in production code. That’s bad habit.
Apart from the overhead, it leaves a sloppy impression to your users. And that is not what you want.

2 Likes

It’s an interesting situation. The error are coming from the C152 aircraft, that I assuming is being used as AI,. I am in the C172.
But even if I “delete” the C152 from my hanger, it remains active in the sim (file is not deleted) … hence my assumption it is being use for AI traffic.
If I manually delete the aircraft from my PC, then when I start MSFS, it “updates” and reloads the files, but it does not show in my hanger, till I go in and seeing it in my Library, ask it to install.
Unfortunately, the errors are associate with Animation, and there is currently no way (?) users can open & explore the model file, to see exactly where the issue is. (YET :slight_smile: its coming soon !!!) I am guessing it is an animation missing from one of the Lods

But as @InhumanCash2369 says, a bad habit to ignore fixing errors that so clearly display to the user/addon developer … Just Sloppy and something that should never past QC before a release / patch.

The errors themselves are not such a big deal, its more the display of Sloppiness, and lack of apparent QC,

1 Like

It actually means a male sex organ. As in “I got my plonker out to have a pee”

As such it’s quite descriptive of that.

Naturally it’s also used as a mildly derogatory term, often on TV shows as an alternative to language which may not be as appropriate for television.

Simple answer: because nobody cares. “Dev console” is also not exactly “exposed to the user”.

As you certainly know, what you see there are apperently missing autogenerated link targets to special animations. And I just checked that even though the clock knob comes with a message about a missing animation, it’s animated nevertheless, assumably via default behaviour.

So just because there’s an unresolved link target (which apparently is expected considering the default behaviour), it doesn’t mean that there’s a problem that needs to be fixed, nor does it mean that the issue is actually fixworthy.

I’d suggest turning off the messages. They I suppose you’re happy, and that’s an easy fix indeed.

1 Like

But in an annoying way they are exposed to the user after all: the more error messages there are logged in the dev console, the more frequently the loading circle in the lower right corner appears, even outside of dev mode.

2 Likes

I can’t comment on the effort required to stop the errors from occurring but I have noticed they can have an effect on some stuttering I get occasionally.

Since day 1 of the sim I sometimes get a problem where the spinning circle in the bottom right appears at a regular 2 second interval continuously, when this occurs I also see a half second pause which coincides with the spinning circle I.e every 2 seconds.
This is obviously very annoying and immersion breaking.

The way to solve this is to open the dev console and delete all the error messages, then close dev console and return to flying. This stops the pauses and the spinning circle.

So if there is an easy fix it would be good if they could implement it

1 Like

I TOTALLY agree. If we can see them, why are they there? Wouldn’t that be the first thing you do is fix these issues?

1 Like

Not only is it bad form, but, the software is spending time looking for this information that for whatever reason was forgotten or whatever by the coder(s) (do they use a software tool to build the info as opposed to hand coding?) building the plane, compute time that could be used elsewhere.

Exactly. If it’s generating errors, its doing something it doesn’t have to do.

1 Like

I have a new criteria for deciding on which 3rd party dev I will buy from and support.

The Number of Error messages that their products produce in the Dev Console, which I relate directly to how sloppy they are in producing & testing their products.

No name mentioned – If you are curious go check out your own Dev Console error messages :slightly_smiling_face:

1 Like

4 MONTHS LATER –

A lot of new planes now in MSFS – some by Asobo, some by “respected” / establish 3PDs, and some by enthusiastic members of the community.

And what comes with all these new planes ? A whole slew of additional errors.

So, do these errors really matter ? Some are saying NO, and its not for the non-developers to even look at them.

But the point is, Obviously the developers themselves are not looking at them, because so many are just stupid, careless coding mistakes – and now many are quite clearly logged with more than enough details, to be able to EASILY fix then, if only the developers would make the effort,

Some do - Good Job - some obviously do not care, and it is becoming quite obvious who those sloppy Devs are.

The interesting thing is that there seems to be a direct correlation between a plane’s errors in the Dev console, and the number of people posting about issue with these planes, with little or no response from their developers.

So, one end up with, after a 30 minute flight, literally with 10,000 + errors, most of which are just stupid coding mistakes, and may or may not be affecting how the plane functions… (looking at a sample of them, YES - they will defiantly alter how the plane functions) !!

I am not asking for the impossible.

As a volunteer member of a 3PD MSFS plane development team, I know from personal experience with MSFS, that it is possible to put out a plane that generated zero Dev Console errors.

1 Like

BTW … Asobo have done a great of greatly improving the detail description of errors in the Dev Console in recent SU updates,

Now it’s up to the Plane Devs (and Scenery Devs) to step up and fix their products, and hopefully by doing so, make a significant improvement to the overall stability of MSFS

1 Like