Modcraft - The community dedicated to quality WoW modding!

Content creation => Level Design => Topic started by: Dr.Manhattan on June 28, 2012, 02:25:05 pm

Title: Some m2 not visible
Post by: Dr.Manhattan on June 28, 2012, 02:25:05 pm
Hi... In noggit me create location with m2 and WMO

In game Some m2 not visible, but after relog thay again visible
Title: Re: Some m2 not visible
Post by: Vel on June 28, 2012, 07:32:39 pm
Quote from: "Dr.Manhattan"
Hi... In noggit me create location with m2 and WMO

In game Some m2 not visible, but after relog thay again visible
you have the same (repeated) unique IDs in the doodads.

As far as I can remember who it was already a problem. Perhaps this topic will help you (http://modcraft.io/viewtopic.php?f=10&t=1789) <<<clickable
Title: Re: Some m2 not visible
Post by: Dr.Manhattan on June 28, 2012, 09:43:03 pm
Tallis not opened that adt =(
Title: Re: Some m2 not visible
Post by: Zim4ik on June 28, 2012, 10:03:58 pm
Try to use newer versions of noggit. Like sdl 1.1 not noggit 3
Title: Re: Some m2 not visible
Post by: Dr.Manhattan on June 28, 2012, 10:55:22 pm
Facepalm, me use only SDL 1.1
Title: Re: Some m2 not visible
Post by: Vel on June 29, 2012, 02:25:16 am
Quote from: "Dr.Manhattan"
Tallis not opened that adt =(
what? I was referring to another



Quote from  topic(which you have not read) - viewtopic.php?f=10&t=1789 (http://modcraft.io/viewtopic.php?f=10&t=1789" onclick="window.open(this.href);return false;)


how to solve this problem:


Quote from: "Filipsons"
Problem solved!
Solution: Resave in rev.120
as simple as that...  thanks schlumpf, Steff, Vel and Eluo

in russian for manhattan:
[spoiler:1dcx809m]я тебе дал тему где парень решил у себя такую же проблему, а ты даже не удосужился ее всю до конца прочитать, это как тебе дали автомат и патроны, а ты дергаешь курок не понимаешь что он не стреляет лишь потому что ты не вставил эти самые патроны я тоже юзаю 1.1 и за 5 минут догадался как решить эту проблему другим способом, не тем тот что указан выше. Но боюсь ты его просто не поймешь, как и большинство всего что я пишу[/spoiler:1dcx809m]
Title: Re: Some m2 not visible
Post by: Dr.Manhattan on June 29, 2012, 07:26:05 pm
I have read this topic and as you don't read this adt is not opening in taliis and resaving in rev. 120 didnt help me.
in rus for Vel
Твоя метафора неразумна, если ты думаешь что все настолько тупы чтоб не посмотреть решение. Я читал сей топик задолго до создания темы , ресейв в 120 реве не помог, а твой ломаный инглиш дал мне понять только через 4 минуты что ты наклацал про талис, но, к сожалению, сей адт в нем не открывается, по этому, логичто что я создал новый.
Title: Re: Some m2 not visible
Post by: Zim4ik on June 29, 2012, 08:27:41 pm
Russian:
Лол, его ломаный инглиш? Ты бы посмотрел на свой со стороны. И не фейспамль, когда тебе пытаются помочь.
Title: Re: Some m2 not visible
Post by: Steff on June 29, 2012, 10:57:36 pm
1. DONT use Taliis on your ADT.
2. UID Problem. You need to recalc you UIDs. If not all parts of you mapp where loaded during you add new models the UID noggit set could be the same as a model already located on another part of your map. 2 Models with same UID dont get displayed.
Title: Re: Some m2 not visible
Post by: Vel on June 30, 2012, 09:07:53 am
Quote from: "Steff"
1. DONT use Taliis on your ADT.
2. UID Problem. You need to recalc you UIDs. If not all parts of you mapp where loaded during you add new models the UID noggit set could be the same as a model already located on another part of your map. 2 Models with same UID dont get displayed.

you're partly right

when any edit in taliis a little break your ADT, but taliis has have awesome function - "generate uniq IDs of the doodads" ... but you can create backup and overwrite uniq IDs in taliis, then extract doodads data via fileinfo.exe, then delete edited in taliis copy(first copy) of the adt. and last step> load information of the doodads in second copy (which is not edited in taliis).

but this way has one problem ... fileinfo  loadinfo 95% of cases - causes crash "the memory could not be read  written blah blah ..."

I have occurs this problem regularly, it would be nice to create a new function for sdl "Generate new uniqie doodads IDs"
Title: Re: Some m2 not visible
Post by: Steff on July 01, 2012, 12:21:08 am
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.
Title: Re: Some m2 not visible
Post by: Vel on July 02, 2012, 08:46:50 am
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.

it would be really nice :O
Title: Re: Some m2 not visible
Post by: Steff on August 31, 2012, 09:08:14 am
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?
Title: Re: Some m2 not visible
Post by: schlumpf on September 01, 2012, 01:27:12 pm
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?
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.
Title: Re: Some m2 not visible
Post by: Steff on September 01, 2012, 02:20:23 pm
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.