Modcraft - The community dedicated to quality WoW modding!
Featured => Noggit => Topic started by: deewad on November 20, 2012, 09:24:25 pm
-
Well as the title says, Im unable to import WMO's into noggit, m2's import just fine, I got 2 different WoW folders for both of them, I created a new continent, Does same thing, So maybe someone can help me.
-
Same error here. I had to resort to importing WMO's from Cryects. But once you import them, you can copy paste like always.
-
Same here :/
-
What are your locals?
-
enUS here
-
Same, enUS
-
Should be enGB
-
It was never a problem before, enUS worked fine on older builds. I haven't tried the latest build but the bug crept in recently.
-
Question, do you ALL use the version
v0.7.0.1 r128
of modelviewer that is linked in the FAQ. I hade someone used 0.5.08 and he can import m2s but no WMOs.
-
I'm having the same problem. Yes I'm using the correct WoW Model Viewer. But WMV isn't the problem. Even when I go into the "Import.txt" and place the path for a WMO object, it doesn't work. As the others above mentioned, M2s work just fine but WMOs do not. And I'm also on enUS local.
-
The locale is completely irrelevant. The log might be relevant. Try opening some empty world (qa_dvd, development, exteriortest), import the WMO once via import.txt, once via wmv log. Have nothing else in those files. Save. Close.
-
The only reason I mentioned my local is because Steff asked for it. Anyways, I did exactly as you told me to. They still didn't show up when I tried to place them but here's the logs. I included everything I thought would be helpful.
-
Well, in that log, there is an WMO inserted and saved. With WMV, the problem might be that loading an WMO loads a lot of other files (including models) after loading a WMO, which might confuse whatever Steff wrote.
-
I suppose that could be a contributing factor but don't forget this isn't a WoW Model Viewer problem. The method using the Import file doesn't work either. I click "Import," and the menu comes up with my WMO listed just fine. But when I go to click on it nothing happens. I tried this exact method using an M2 object, and that one worked soo...
Also, I did notice that the log claims the WMO was placed, just as you pointed out. But even after exiting Noggit and reloading the file, it still doesn't show up on my screen. I checked under the terrain, and high above to make sure it didn't spawn at the wrong elevation. Still, nowhere to be found.
-
I know this isn't a model viewer problem. I always hated that import hack. It is completely broken. It is impressive M2s work.
Still, it does something with WMOs, so it is 'somewhere'. No idea where though.
-
Okay now things are just getting silly and weird. For a moment, it worked. I did nothing different this time but some how both methods were working for WMOs. So then I closed Noggit and tried it again. I did exactly as I just did. Doesn't work now. Sigh...
Edit: I found a temporary solution! (For me at least)
Alrightie, this is pretty much the silliest most unheard of solution, and as far as I can tell it makes no logical sense whatsoever. First off, if I load up Noggit and immediately try to place WMOs, it won't work. However, if I instead find another WMO within the editor and copy/paste it, I am then able to start importing WMOs. I imagine none of you have any idea what I'm talking about so I'll write it out step-by-step.
1. Start Noggit
2. Load an area that already has WMOs or M2s placed in it.
3. Click on a pre-existing WMO or M2. Copy it.
4. Paste the WMO or M2 wherever you like. Then delete it.
5. ??????????????????
6. Profit. You can now import WMOs.
Anywho, I really hope that helps you guys out. Obviously this doesn't fix the issue long-term. But it'll work for now.
-
ANd if you do a model import do you use the shortcuts or turn off auto selection, mark a chunk and use then the import. It will not work without an selected chunk. The most people are to lazy to read the manual where this is explained.
1. Press c till you get the yellow selection triangle
2. Press Shift + F4 to turn OFF auto selection or use the menu to do this. > Now the triangl dont follow the mouse automatic.
3. Now select a triangle.
4. Now use the import functions to get a model in
You can also select an existing model to past not on triangle but on the postition of the model.
-
Don't get me wrong Steff, I always read the instructions before posting. I've been trying to select the chunk first the entire time, and I tried it again just to be thorough. It simply doesn't work. I open the editor, pick a location, change my cursor to the triangle, turn off auto-select, then either click the ground or another model. It changes nothing. In fact it actually crashed my client when I was using Windows XP Service Pack 2/3. So I turned off compatibility mode and it stopped the crashes, but the method you suggested still doesn't work.
-
Just face it, Steff. UX and the feature itself is broken. The only relevant thought with noggit is to abandon the SDL version as said two years ago.
-
But for me everything works fine. I use it every day and added hunder of models without any porblem.
And SDL is the only useable version. There is to much work to do on the QT to get it working so every modder also coding on it to get new features need to spend too much time and lose motivation.
-
OMFG Xapzi thank you very much loooooooooooooooooooooooool that "silly and weird" solution its just what i needed :o
-
You're very welcome. I'm glad to hear that I'm helping so many people with this problem. I know it was a nasty one for me to deal with and took several hours to come up with a solution.
Steff, if you don't mind, I really think this should be mentioned in the FAQ. I know that you personally haven't experienced this bug on your machine, but me and several other users have, and I think it would be beneficial for all of us if my solution was included in the FAQ.
-
I think it caused by the little option in Noggit config FarZ=2048 I've tried to set FarZ=4096 since that I've not got bugs with adding WMOs (also helpes to cleane log). I agree with Xapzi i think this ways of solving such problem must be in FAQ.
-
Wish I had the same luck Fearless. I tried messing with that config just now and it didn't fix the bug for me.