Forum > Level Design

Some m2 not visible

<< < (3/3)

Steff:
I did also implement once the function that noggit just qwirte new UIDs during save. The problem with this way, what is neraly the same as doing it over the loadinfo/filinfo cmd, is that you have ONE model that is located on the boarder of an ADT on both ADTs it is located.

If you have it not on both it flickers or disapperas.
If it is on both ADTs and have different UIDs its not one mode but 2

So if you do it with noggit you get on every save one new different UID for every model on corners. So tehy double. You know the checkerboard and rice thing ;)

The only way whould be to have an external list of all UIDs on the map and test after creation of new UID that it is not still in the list. This works as long you only work with one guy on the map. If you work with more the list must be provided by a webservice to all clients. And all noggit clients must be online during model inserting and copy.

The problem is that you can not just change all UIDs on save. Because you get a new problem with the next not saved adts near the one you save. So if you change one you have to save all ADTs of the map.

Or write a tool that open all adts, creats the UIDs set them to the models and write all adts again on the HD.
And best it tests if there are double models on the exact same position during this. This can also happen if you just copy a model and past it if the source model is stil selected.

Vel:

--- Quote from: "Steff" ---Or write a tool that open all adts, creats the UIDs set them to the models and write all adts again on the HD.
d.
--- End quote ---

it would be really nice :O

Steff:
I read it just now :)
Taliis > "generate uniq IDs of the doodads"

Noggit prevent double UIDs on all ADTs you have in Ram (loaded) The problem is that there can be one that is on an adt that is some adts away. Taliis only fix UIDs on current ADT you have loaded what is not needed anymore.

An other idea. What about an position depending UID hash. THis whould be same on both saved IDs and uniqe on hole map. Will think abou this. Bernd what do you meen. Do we get some cord depending math that lead so real uniqe ids?

schlumpf:

--- Quote from: "Steff" ---An other idea. What about an position depending UID hash. THis whould be same on both saved IDs and uniqe on hole map. Will think abou this. Bernd what do you meen. Do we get some cord depending math that lead so real uniqe ids?
--- End quote ---
In theory should be possible. Will break on multiple models at the same position. The hash would have to include x,y,z,rotation,tilt,yaw,file name, map id.

Steff:
I think

x,y,z,rotation and file name

is enough.
UIDs can be the same on different maps.
If we have the same model on same pos and rotation it should be deleted.

Navigation

[0] Message Index

[*] Previous page