• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 Duplicate GUID

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
6,638
Country
us-wisconsin
I just had an instance of a gltf I made that had a guid conflict. The model was processed through MCX, but that was not the problem. The guid did work in the past, but the new update apparently included a guid that matched mine. First time that ever happened to me. The end-result was my model was replaced by the new MSFS model. So it can happen, though extremely rare. So if your placement shows the wrong model, you may need to change it's guid in the gltf XML, and place the model with the new guid.
 
I just had an instance of a gltf I made that had a guid conflict. The model was processed through MCX, but that was not the problem. The guid did work in the past, but the new update apparently included a guid that matched mine. First time that ever happened to me. The end-result was my model was replaced by the new MSFS model. So it can happen, though extremely rare. So if your placement shows the wrong model, you may need to change it's guid in the gltf XML, and place the model with the new guid.
How (how much) lucky are you to repeat an identical GUID ?
this thing is extremely rare ... Prefers to win a lottery 😁
 
How (how much) lucky are you to repeat an identical GUID ?
this thing is extremely rare ... Prefers to win a lottery 😁

Oh - nice one. Since GUIDs are supposed to be random and should be generated fresh each time one is needed it seems someone copied?
 
It's not something unknown because I have heard of it before, but extremely rare to the point that you have more chance of being struck down in a thunderstorm.
 
"128-bits is big enough and the generation algorithm is unique enough that if 1,000,000,000 GUIDs per second were generated for 1 year the probability of a duplicate would be only 50%. Or if every human on Earth generated 600,000,000 GUIDs there would only be a 50% probability of a duplicate."

Jup, extremely rare ^^
 
I wonder if the problem is that some don't use randomly generated GUIDS. I remember a library tool for FSX which just incremented the GUID for each new model, and I've recently seen someone post a MSFS XML file with incremented GUIDS. Make sure you use a proper generator for every GUID!
 
I think it was an Asobo object that was part of an update that matched mine. Originally, my object displayed just fine. Weeks later, it displayed the wrong object. If so, it actually happened to Asobo, not me.
 
Here is some interesting info about just how unique GUIDs "should" be: :idea:



As an alternative to use of online tools for GUIDs:


Here is some info about how to generate GUIDs on one's own Windows computer via PowerShell or the Command Prompt:



FYI: Don Grovestine (aka "gadgets") included a GUID generation feature via .NET in this utility that has been available here at FS Developer for years:



NOTE: Years ago, a IMHO 'bad' idea used in certain tools generated sequential GUIDs based on code from one's network interface card or router.

Lets just hope Asobo does not get mixed up with all the GUIDs it may be attempting to monitor on each "unique" MSFS-2020 user computer: :rotfl:



GaryGB
 
Last edited:
I just had an instance of a gltf I made that had a guid conflict. The model was processed through MCX, but that was not the problem. The guid did work in the past, but the new update apparently included a guid that matched mine. First time that ever happened to me. The end-result was my model was replaced by the new MSFS model. So it can happen, though extremely rare. So if your placement shows the wrong model, you may need to change it's guid in the gltf XML, and place the model with the new guid.
Hi, how did you find this conflict and the corresponding GUIDs?
 
I found this by resuming work on my text scenery...C59. One of my models was replaced by another model. I didn't do it, and hadn't touched that model or it's placement in months. Changing the GUID was an 'educated' guess.
 
Back
Top