Difference between revisions of "Bug list"
Jump to navigation
Jump to search
imported>Black RL |
imported>Black RL |
||
| Line 10: | Line 10: | ||
**'''''Solution for this problem:''''' | **'''''Solution for this problem:''''' | ||
Create a new global variable (Object window -> global), see picture: | Create a new global variable (Object window -> global), see picture: | ||
[[File:CKTUTLoadBug01.jpg]] | [[File:CKTUTLoadBug01.jpg]] | ||
Put the load doors as you normally do but don't check the teleport flag, put a XMarkerHeading in front of the doors (object window -> static), name one XMarkerHeading Objective001 and the other one Objective001A (that way you know that they are connected). Another set of load doors should be called for example Objective002 and Objective002A. See pictures: | Put the load doors as you normally do but don't check the teleport flag, put a XMarkerHeading in front of the doors (object window -> static), name one XMarkerHeading Objective001 and the other one Objective001A (that way you know that they are connected). Another set of load doors should be called for example Objective002 and Objective002A. See pictures: | ||
Revision as of 17:41, 17 June 2012
Version 1.6.89.0
You can check the discussion in the official forum here
- Interior cell has a static rm limit
- Load door in interior cell that connects to load door in exterior cell causes ctd
- Cow same exterior cell causes blue screen
- Video showcasing the bug
- Forum discussion
- Solution for this problem:
Create a new global variable (Object window -> global), see picture:
Put the load doors as you normally do but don't check the teleport flag, put a XMarkerHeading in front of the doors (object window -> static), name one XMarkerHeading Objective001 and the other one Objective001A (that way you know that they are connected). Another set of load doors should be called for example Objective002 and Objective002A. See pictures: