I'm just wondering if anyone else has encountered this bug:
Modder1 creates a creature and names it "mob1".
Modder1 then uses B2B to send this creature to Modder2.
Modder2 renames the creature to "mob2" and then uses B2B to send it back to Modder1.
Instead of recognizing that its the same file renamed and carrying the rename over onto Modder1's machine, it treats it as a new file and imports it so now Modder1 has two copies of the same creature with different names.
Do this on a team of 5 with two dozen renamed resources and have it go unnoticed for 2 months and then realize how much havok it has wrought.
Everyone using different versions of the assets and when they send the B2B files to each other, some people dont have the different versions and the dependancies break and files wont open and cutscenes dont work and AGGHHHHHHH!!!!!!!
*sob*
B2B renamed file bug
Débuté par
Mloren
, mai 25 2011 02:20
Retour en haut
#2
Posté 26 mai 2011 - 06:13
Proleric
-
- Members
- 2 360 messages
Sorry to hear that.
Since you ask, the issue is documented, though the section could be rewritten more clearly. Not much help after the event, I appreciate.
Assuming you've been using the same resource name, changing properties such as the Name displayed in game, Builder-to-Builder will do what you want, but the resource must be checked in before loading a new version. Otherwise, it creates a new resource renamed resource_01. This is a feature, not a bug.
However, if you mean that modified versions have been given a new resource name (by duplication), there's no way Builder-to-Builder can know it's the "same" resource.
To be honest, most of us found out about this the hard way, though in hindsight it is apparent if you read the log carefully.
Since you ask, the issue is documented, though the section could be rewritten more clearly. Not much help after the event, I appreciate.
Assuming you've been using the same resource name, changing properties such as the Name displayed in game, Builder-to-Builder will do what you want, but the resource must be checked in before loading a new version. Otherwise, it creates a new resource renamed resource_01. This is a feature, not a bug.
However, if you mean that modified versions have been given a new resource name (by duplication), there's no way Builder-to-Builder can know it's the "same" resource.
To be honest, most of us found out about this the hard way, though in hindsight it is apparent if you read the log carefully.
#3
Posté 27 mai 2011 - 04:38
Mloren
-
- Members
- 16 messages
Actually this is a different issue:
It's a new resource name but not by duplication. By right clicking the resource and going Properties and then changing the resource name there.
This is clearly renaming the resource, not duplicating it so the toolset should recognize this and when you use B2B to send the files to someone, it should carry over the rename of the file rather than creating a new one.
It's a new resource name but not by duplication. By right clicking the resource and going Properties and then changing the resource name there.
This is clearly renaming the resource, not duplicating it so the toolset should recognize this and when you use B2B to send the files to someone, it should carry over the rename of the file rather than creating a new one.
#4
Posté 27 mai 2011 - 06:54
Proleric
-
- Members
- 2 360 messages
Ah, I see.
Problem is, the resource name is the unique identifier for a resource. So, if you change it, you are implicitly duplicating to a new resource and deleting the old one.
There's no way Builder-to-Builder can know it's intended to be the same resource.
Problem is, the resource name is the unique identifier for a resource. So, if you change it, you are implicitly duplicating to a new resource and deleting the old one.
There's no way Builder-to-Builder can know it's intended to be the same resource.
