When moving beacons, after receiving the warning about moving an object, they somehow turn into asteroids. Very odd. When moving markers, their radius reverts to 1km. After saving, they seem to remain as set, but I did have a review that mentioned coming across a rock in space where a beacon should have been, so it may be happening after publish as well.
I have also seen similar odd behavior with wall lockers. I placed several of them on a map (the version where the locker door is closed), then I go to preview and the locker doors are opened.
I double checked to make sure it was the closed version, deleted and replaced, moved them to another spot...nothing could keep them from opening.
I'm actually starting to wonder if my custom map is haunted! :eek:
[SIGPIC][/SIGPIC] Command Officers of the USS Wyvern (from left to right): Aurellia Eshkah (Tactical); Indigo Shae (Engineering); Nysiay Chysiayki (VA, Ship Captain) Jeclia Sek (Science); Vally Mantivour (Security)
I have also seen similar odd behavior with wall lockers. I placed several of them on a map (the version where the locker door is closed), then I go to preview and the locker doors are opened.
I double checked to make sure it was the closed version, deleted and replaced, moved them to another spot...nothing could keep them from opening.
I'm actually starting to wonder if my custom map is haunted! :eek:
This isn't a bug per se. The lockers are actually setup to randomly choose between several different versions. There are a number of consoles, spaces bases, and other objects that behave this way, but some are poorly marked.
Keeping in mind that these date back to the original release of the Foundry, I believe they were made this way to allow variety to repeated objects without requiring the author to stagger which version. Obviously this can cause problems for more skilled authors who are attempting to build more specific setups, but when the Foundry was first created, they were aiming for simplicity.
EDIT: What Cap P.F.Dennis is describing though doesn't sound right.
Fast forward to 6:00pm EDT on 6/24/13 and the fact that I have spent every minute since 4:00pm trying to log in and cannot. It's either for "an unknown reason" or "Dynamic Patch Failure: Connection Idle for too long". Now we're all locked out. Button just went gray.
When moving beacons, after receiving the warning about moving an object, they somehow turn into asteroids. Very odd. When moving markers, their radius reverts to 1km. After saving, they seem to remain as set, but I did have a review that mentioned coming across a rock in space where a beacon should have been, so it may be happening after publish as well.
I'll look into this. Can you let me know what assets are being affected?
So far, it is just those mentioned. Whenever a Blinking Beacon-FX is moved, the object title remains the same, but in the object tab beneath, and on the map, the object changes into an asteroid. Whenever a marker is moved, it will reset to a radius of 1km.
On a side note, I'm timing preview load times at 4 minutes. It is 5:00am here on the East Coast, 6/26/13.
This transposition happens to any object moved on a legacy (mission map created prior to season....4 I think) missions most specifically. Basically its like when you move it and choose yes I think, it points the item index to some other part of the object array, on ground maps I think it was a rock wall?
I dont know this happens with any 'newer' missions, just those that predate the big changes that, again I think happened in S4.
Comments
I double checked to make sure it was the closed version, deleted and replaced, moved them to another spot...nothing could keep them from opening.
I'm actually starting to wonder if my custom map is haunted! :eek:
Command Officers of the USS Wyvern (from left to right):
Aurellia Eshkah (Tactical); Indigo Shae (Engineering); Nysiay Chysiayki (VA, Ship Captain)
Jeclia Sek (Science); Vally Mantivour (Security)
This isn't a bug per se. The lockers are actually setup to randomly choose between several different versions. There are a number of consoles, spaces bases, and other objects that behave this way, but some are poorly marked.
Keeping in mind that these date back to the original release of the Foundry, I believe they were made this way to allow variety to repeated objects without requiring the author to stagger which version. Obviously this can cause problems for more skilled authors who are attempting to build more specific setups, but when the Foundry was first created, they were aiming for simplicity.
EDIT: What Cap P.F.Dennis is describing though doesn't sound right.
I'll look into this. Can you let me know what assets are being affected?
On a side note, I'm timing preview load times at 4 minutes. It is 5:00am here on the East Coast, 6/26/13.
I dont know this happens with any 'newer' missions, just those that predate the big changes that, again I think happened in S4.