mirror of
https://github.com/Relintai/godot-lportal.git
synced 2024-11-23 05:17:20 +01:00
Update INSTRUCTIONS.md
This commit is contained in:
parent
e1025609ef
commit
277fe59930
@ -147,9 +147,9 @@ The number 0.0 is the radius of the DOB in the visibility system. All DOBs are m
|
||||
|
||||
If a DOB is being culled (popping out of view) when it should not, it is normally because the bounding radius needs to be larger. On the other hand, too large a radius will make the DOB render when it is not necessary, so it is a good idea to tweak this value. It is in Godot world units, so you may be able to simply measure you object in the IDE.
|
||||
|
||||
* Each frame, call `dob_update(cam)` to keep that DOB updated in the system
|
||||
* Each frame, call `dob_update(dob_node)` to keep that DOB updated in the system
|
||||
|
||||
If the DOB is not moving, or you want to deactivate it to save processing, simply don't call update again until you want to reactivate it. There is no need to call dob_update on the selected camera, it will be updated automatically.
|
||||
If the DOB is not moving, or you want to deactivate it to save processing, simply don't call update again until you want to reactivate it. Note that there is no need to call dob_update on the selected camera, it will be updated automatically.
|
||||
|
||||
* When you have finished with a DOB you should call `dob_unregister(cam)` to remove the soft link from the system. This is more important when you are creating and deleting DOBs (say with multiple game levels). If you call rooms_release when unloading a level and want to keep DOBs in between levels, it is crucial that you do not update them until you have re-registered them after calling rooms_convert to create the new level (you will get an error message otherwise).
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user