Modcraft - The community dedicated to quality WoW modding!
Featured => Noggit => Topic started by: -Dave on June 06, 2014, 07:47:52 pm
-
Hey guys,
I've been a bit of an off/on hobbyist for a while. Recently reinstalled Windows from scratch on the exact same system with no new hardware or anything. Noggit used to run perfectly fine on the previous version. The only change is I'm using Windows 7 64-bit now as opposed to 32 previously (I don't know why, but the computer had a 32 bit OS installed despite having hardware to support 64.)
My log from SDL 1.2 is here: ( http://pastie.org/9265202 (http://pastie.org/9265202" onclick="window.open(this.href);return false;) )
and SDL 1.3 won't start at all. ( http://prntscr.com/3q954m (http://prntscr.com/3q954m" onclick="window.open(this.href);return false;) )
Cheers,
Dave
-
" 1469 - (FreeType.cpp:133): [Error] FT_New_Face failed (there is probably a problem with your font file) "
- are you using patch with font changes ?
- check your fonts inside of noggint File
may its somethign of them
-
Both Noggits are fresh from the forums - 1.2 from the tutorial pack and 1.3 from the thread. Only thing I've done is change the config to point it at my client, which looks like it worked fine since it's loading SOME files.
Ideally I'd like to use SDL 1.3 but since it won't even start, I have no logs to tell me why it's being moody.
/E: Oh, and the DBCs it's saying it's having problems with are actually there: http://prntscr.com/3q9p32 (http://prntscr.com/3q9p32" onclick="window.open(this.href);return false;)
So it's not like they don't exist or anything.
-
Noggit works fine with all windows versions. I used it from xp up to 8.1 in 32 and 64 bit.
As kt tells you that it cant open the files. You have a access probelm.
Check your folder rights and the read only option in folder propertis of the main folder.
Often hapens after reinstallations and copy wow over.
-
Awesome, 1.2 works fine now, cheers.
Any idea why 1.3 is complaining? Still no change on that after fixing the folder permissions. :)
-
Awesome, 1.2 works fine now, cheers.
Any idea why 1.3 is complaining? Still no change on that after fixing the folder permissions. :)
try open wow launcher for some seconds maybe 4 to 5 and close it I did that when I converted to 64 windows 7 I hope it help you
-
Could you mirror your launcher for me please? I've just noticed that the wow I got off a torrent just came with wow.exe - I did try running that to the login screen a few times, but there's no harm in giving the launcher a go. :)
/E: Never mind, forgot there should be one in wow-base.MPQ. n_n
//E: Extracted the launcher, let it download the new launcher and some "updated tools" (looked like it only downloaded the fall of the lich king cinematic) and closed it when it began patching to 4.0.0 - ran SDL 1.3 and still no change. :/
-
Logfile and config file on pastbin.
-
The program is crashing before it even starts to do anything - there is no log file, just a memory reference
( http://prntscr.com/3q954m (http://prntscr.com/3q954m" onclick="window.open(this.href);return false;) )
Here is the config file though.
( http://pastebin.com/tnCwj7M4 (http://pastebin.com/tnCwj7M4" onclick="window.open(this.href);return false;) )
/E: 1.2 works perfectly fine - no problems with that at all since sorting out the folder permissions. This is for 1.3
-
Try other download source. Soumd lime the exe is not right or importand files are missing.
-
Just give up on 1.3 and use 1.2. Too many bugs in 1.3 that don't justify the new features IMO.
-
Could you sort out the "official" download then Steff?
I got this one off a mirror someone posted on the thread, since your link on the first post no longer works.
Cheers.
-
Just give up on 1.3 and use 1.2. Too many bugs in 1.3 that don't justify the new features IMO.
To many bugs. Interesting. In know only one reported to me. Second save kills or duplicates models.
I will have a look for dl source of my last compile.
-
Cheers buddy, hopefully we can sort this out painlessly. n_n
-
Heyo guys, just saying I'm still having issues here. :)
Consider this a 'bump' post of sorts.