Forum > Noggit

[SOLVED]  Insant crash upon loading a map

(1/2) > >>

nasteey:
Whenever I try to open either a custom or a "blizzard" map, NoggIt closes automatically.
I've just got my access to beta and I've read almost all the topics, but couldn't find a solution to this problem (and to tell the truth, I don't understand the log file). Here is my log file and config.

--- Code: ---http://pastebin.com/X3LjPGAg
--- End code ---
[spoiler:2zqvs03m]# This is a config file tamplate. To use it rename into noggit.conf and set your optiones

#Edit this to your WoWFile!!!
Path = D:!JátékokWorld of Warcraft RP

#Edit this to your Project-Directory and uncomment if you want to use it!
#ProjectPath = E:project01

#Set this to the file where you will impor models from (the modelviewer log for example :) )
#ImportFile  = Path to ModelViewer logfile

#The Far clipping value. Set to 2048, 3072, 4096 etc. for a further look. Higher values need more 3d power.
#1024 is the standart value and will be taken if you do not set this value.
FarZ=2048[/spoiler:2zqvs03m]

Steff:
#
946 - (MPQ.cpp:47): [Debug] Opened archive D:!JátékokWorld of Warcraft RPData/patch-d.MPQ
#
946 - (MPQ.cpp:47): [Debug] Opened archive D:!JátékokWorld of Warcraft RPData/patch-t.MPQ

Don´t use a wow for noggit source with custom MPQs in!

schlumpf:

--- Quote from: "Steff" ---#
946 - (MPQ.cpp:47): [Debug] Opened archive D:!JátékokWorld of Warcraft RPData/patch-d.MPQ
#
946 - (MPQ.cpp:47): [Debug] Opened archive D:!JátékokWorld of Warcraft RPData/patch-t.MPQ

Don´t use a wow for noggit source with custom MPQs in!
--- End quote ---

IT IS COMPLETELY IRRELEVANT TO USE CUSTOM MPQS AND WE NEED TO SUPPORT THAT. Seriously.

Custom MPQs are just as fine as original MPQs. Noggit _needs_ to support them. Putting them outside does _not_ help.

Steff:
The this are not that there are custom MPQs in. The thing is that they are most time full of bugs and crash noggit. So if noggit crash,  first exclude all common problem sources.

nasteey:
I've removed the custom MPQs, but the problem still occurs. However, the problem is gone in rev120.

Navigation

[0] Message Index

[#] Next page