neux on 22/3/2015 at 00:50
I have a MUST FIX problem.
Objects are disappearing during gamemode in dromed or when played normally.
When i start gamemode the objects are there but when i move away from them, say diagonally across the map I'll actually see them disappear. Certain area disappears actually. It's not where i started building nor where i finished.
Objects are identical to objects positioned around the mission.
Same happens when i play it normally. Additionally if i restart the game, the objects are not there. I have to restart the game in order for to appear again.
I've increased max_ref, couldn't think of much more. I'm stuck.
Another question:
I can't optimize, i run into errors. Is it necessary to optimize a mission?
For limitations sake, heres my portalize info:
Inline Image:
http://www.imageupload.co.uk/images/2015/03/22/out.png(
http://www.imageupload.co.uk/images/2015/03/22/out.png)
Lady Rowena on 22/3/2015 at 02:06
You MUST optimize your mission! You better stop and try to fix the errors before it's too late. What errors are you having?
LarryG on 22/3/2015 at 02:21
What physics is set on the objects? If OBB you MUST set Physice > Model > Controls: {Location, Rotation; ... } whatever else you do. Without that, they will fall out of view before you get into game mode.
Oops. I jumped to conclusions ... This sounds like something else, now that I read your complete post. Something about efficiency settings perhaps ...
darthsLair on 22/3/2015 at 02:29
Almost everyone will experience that error. The best thing is go back to the last 12 terrain brushes you created, and delete one by one until the error goes away after optimizing.
If it was more than 12 keep going back in "brush time" until you find it.
Once you find it, and it optimizes, type this into the command window:
Hilight_check_snap, then enter.
Hilight_do_snap,then enter
Hilight_clear
It is a good practice to use this command after creating a group of brushes to avoid crashes and assertion errors.
Edit: Looks like you can find the vicinity of the error.
Type this into your command window:
vm_teleport 504.02086,552.40121,528.7384
This should give you an idea of where you were working last. What brush.
neux on 22/3/2015 at 02:50
Oh man...
Report gives back coords of are where problem occurs.
I've "vm_teleported" to the position and deleted 5-10 brushes there.
I've had to repeat the process 5 times and now it optimized.
Now there's the grind... :eww:
Tell me...
Must i delete the brush or can repositioning of the brush solve the issue? I suspect it can.
darthsLair on 22/3/2015 at 03:07
Quote Posted by neux
Oh man...
Report gives back coords of are where problem occurs.
I've "vm_teleported" to the position and deleted 5-10 brushes there.
I've had to repeat the process 5 times and now it optimized.
Now there's the grind... :eww:
Tell me...
Must i delete the brush or can repositioning of the brush solve the issue? I suspect it can.
Deleting the brush without saving was just to find the problem. You can re-position it.
Also, try the snap command first. Alot of the assertion errors concerning terrain brushes can be solved by simply making sure the brush is snapped.
Hilight_check_snap
Hilight_do_snap
Hilight_clear
neux on 22/3/2015 at 03:09
Alright, I'll give it a go.
Thanks man!
Yandros on 22/3/2015 at 04:21
Snapping to grid and optimizing often to check for errors is critical to success, as you are learning.
The disappearing objects problem I suspect is too many objects being in view to be rendered, so some just disappear. This was a lot worse in OldDark, but it can still happen in NewDark. When it happens are you somewhere that a LOT of objects are visible?
Le MAlin 76 on 22/3/2015 at 11:26
Never set of grid, and alltime between 12 and 16 (less or more is not forbiden, the extrem minima limit is 11, but less it would be hardcore for dromed :p )