| Grapholina |  posted: Sat Oct 01, 2005 8:14 pm | |
Member since:
2005-03-08
From:
Texas
Posts:
73
| Not sure if this is a bug or not. I cloned a bed, and when I went to get new GUIDs through SimPE, this is what I got. Notice the jump in numbers?
 |
| Inge Jones | posted: Sat Oct 01, 2005 8:51 pm | |
Member since:
2005-03-06
Posts:
1899
| And you didn't have an object with any number in between at other times? |
| Grapholina | posted: Sat Oct 01, 2005 10:13 pm | |
Member since:
2005-03-08
From:
Texas
Posts:
73
| No, ma'm. I document every object I create. I'm very careful of my GUID's.
I didn't explain enough, though. All but the first number are correct.
My first GUID obtained should have returned 012D2074, and instead I got 012D2000. Sorry about that. |
| Inge Jones | posted: Sat Oct 01, 2005 10:23 pm | |
Member since:
2005-03-06
Posts:
1899
| So the database actually handed you a GUID you already used before?! |
| windkeeper | posted: Sun Oct 02, 2005 12:31 am | |
Member since:
2005-03-12
Posts:
79
| I also had the same problem, I got GUID # that ends with "00", even though it wasn't the first object I registered for that range. My object also had multiple GUIDs so I noticed that they were inconsistent. I simply used "get GUID" again to pull a new number and dismissed it as a one-time glitch. But it looks like it might be a bug.
To word it again, SimPe pulled the first number of my registered range instead of the last used number +1.
I will keep an eye on it and post here if it happens again. |
| SolanderCGN | posted: Sun Oct 02, 2005 1:40 am | |
Member since:
2005-03-10
From:
Cologne/Germany
Posts:
41
| Have the same problem and posted it in the german help-thread. No answer until now. Every single object i register for my account is assigned the first GUID of that block.
The reason for me: The GUID block is completed. 255 objects registerd. Used my 2nd account that has not yet been merged with the first, i think, and it works fine for me now.
SimPE does not produce a warning as before, when all GUIDs are used, it just registers the first GUID over and over.
Greetings
Solander |
| SnowStorm | posted: Sun Oct 02, 2005 5:02 am | |
Member since:
2005-03-21
From:
USA
Posts:
415
| I also was issued my 00, but I think that was because when I first got that block, it started me with 01 not 00. |
| quaxi | posted: Sun Oct 02, 2005 2:18 pm | |
Member since:
2006-04-28
Posts:
3154
| Was it the "Southwest Bed Frame ".
I checkd with the Backup Copy of the GUID Database I made before upgrading to the new System, and SimPE did not register the 0 guid so far, so the GUID was still free as SnowStorm already pointed out. |
| windkeeper | posted: Sun Oct 02, 2005 5:59 pm | |
Member since:
2005-03-12
Posts:
79
| I started a new range recently, the first GUID given me was "...01". Then it went 02, 03, etc. Until, I guess, the GUID database upgrade. Thats when SimPe pulled unused "00".
Its beginning to make sense now, its not SimPe glitch, it was a database glitch that is corrected now. Thats why people are getting the first range number, it wasnt used before... And you all just said that, lol! I should read carefully.
Btw, I to experienced the "00" over and over again when by accident used the user name for older range that was already used up. |
| quaxi | posted: Mon Oct 03, 2005 1:16 am | |
Member since:
2006-04-28
Posts:
3154
| That last part should be fixed now to. |
