View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0027963||Runner||Variables (In-Built)||Public||2017-10-03 12:30||2019-06-24 11:57|
|Reporter||Stewart Bishop||Assigned To||Mike Rennie|
|Priority||High||Severity||C - General||Reproducibility||100%|
|Target Version||2.2.3||Fixed in Version||2.2.3|
|Summary||0027963: Variables: layer gets set to -1 when changing room for persistent objects|
|Description|| Persistent object's layers are stuck on "-1" upon re-entering their original rooms.|
When persistent objects arrive in a new room they're layers are set to -1, which is troublesome, but to get around it you can manually set the layer in code. Although all code affecting the layer is overwritten to "-1" when they return to the room they spawned in.
I have attached a project that switches between rooms on key press and attempts to overwrite "-1".
Layer's being set and forced to -1 causes all instance_create_layer(layer) lines unusable and having to manually set the layer when each room has an identical layers is already problematic.
|Steps To Reproduce||1) Import project|
2) Run project
3) Press space a few times
4) See that this works
5) Open the objects room start event
6) Comment out the line setting layer
7) Run the project again and see that once space is pressed the layer functions no longer work
|Tags||fsd, rendering, Runner|
|1.4 Found In|
|2.x Runtime Found In||126.96.36.1997|
|2.x Runtime Verified In||188.8.131.525|
LayerBug.yyz (16,476 bytes)
||Shouldn't this all be fixed in 2.1.1?|
The new behaviour is as follows:
- When transitioning from one room to another, we now try to put persistent objects on a layer with the same name as the one they were previously on. If we can't find one with that name then one is created. This means that the layer ID does still change from room to room, but returning to the original room will return the object to its original layer.