This is a read only copy without any forum functionality of the old Modcraft forum.
If there is anything that you would like to have removed, message me on Discord via Kaev#5208.
Big thanks to Alastor for making this copy!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Cutsforhugs

Pages: [1]
1
Quote from: "Steff"
You can use every 335a extraced maps. Should work with the server.

Would you happen to know a good download location for them?

I searched around, but could only find one that didn't work, guessing it was for 335 and not 335a.

Thanks for the help @ the mods for answering / helping me with my stupid questions, by the way. c:

2
I don't know if this post is still responded to, but is the extractor incomplete?

I've tried twice now to just completely redo the entire set-up to get everything right, but the same map is always missing from the maps folder:

Code: [Select]
Realm running as realm ID 1
Using World DB: TDB 335.49
Will clear `logs` table of entries older than 1209600 seconds every 10 minutes.
Using DataDir ./
VMap support included. LineOfSight:1, getHeight:1, indoorCheck:1 PetLOS:1
VMap data directory is: ./vmaps
Map file './maps/5301243.map': does not exist!

I would gladly just get the map off of the internet, but odds of getting a unupdated mismatch is pretty high. If anyone can obtain the map on the same rev as the guide and post a downloading link it'd be appreciated.

3
Noggit / [WotLk] [TALIIS QUESTION] - Taliis refuses to save WDTs.
« on: December 10, 2016, 07:05:13 am »
I realize this might be considered a bad thread, but I have tried searching around, so I apologize if that's the case.

I've tried re-downloading Taliis to no avail.

Issue: Taliis won't save WDTs when using the "save as..." option. I tried using "save" only, but obviously that puts the file in the Taliis map. Despite failing to save a file in the correct folder, using "scan folder" will still make it search said folder, but it searches for non-existent ADTs.

For reference, it does work for me to just cut and paste it to the correct folder after using "save" and scan from there, but I'm curious if there is an easy fix for it. Only for the sake of convenience though!

I figured it maybe could have to do with administrator privileges, but trying to open "windows for dummies" as admin only produces errors unfortunately.

https://gyazo.com/e5cf4bca24fe18afb91eef0303bb56a5
https://gyazo.com/6d7db643483bcb87f67271c0062bec33

^ Pictures of forementioned!

4
Noggit / Re: [SERIOUS ISSUE] - OffsetFix
« on: December 05, 2016, 02:31:35 pm »
Quote from: "Simple_Spectr"
http://www.model-changing.net/forums/topic/104-solution-for-crashing-software-caused-by-windows-update/
I think this will help.

That did it, thank you. :)

If somebody else have the issue and stumbles here, remember to try the 32bit latest version. That's the one that worked for me and others.

5
Noggit / [SOLVED] - OffsetFix filling CPU and RAM
« on: December 05, 2016, 04:40:36 am »
Hello!

I've been away from noggit for quite a long time, and figured I'd redo the basic tutorial to get a feel for it again. However, when I try to create my own ADT files, OffsetFix will start automatically (even if it doesn't, I'd like to use the fix.bat).

And here comes the issue. All I get is an error message spam stating that OffsetFix can't be opened, afterwards it will immidately start filling my RAM and CPU with copies of OffsetFix until the point of reaching max capacity, making it impossible to do anything and making me do a force-exit on my entire PC.

I have used the set-up for Noggit before (though a year or two ago) and haven't touched anything since I quit, so what could be causing this issue?

The only thing I haven't tried is starting in administrator mode, but at this point after 3-4 attempts I'm more worried for my PC and would rather hear for alternatives before I try that.

Any help is appreciated!

6
Noggit / Re: [SOLVED] - [Noggit SDL1.3] - Crashes on start-up.
« on: April 08, 2014, 08:39:05 pm »
I mean pick a water type.

Like, the water tool by default says Water type: "0 - Unknown". I then enter the window where you pick the water type, and see "1 - Water, 2 - Ocean, 5 - Lava" etc. but, I can't pick anyone of them. No errors or anything, they just aren't clickable. None of the water types are.

7
Noggit / Re: [ISSUE] - [Noggit SDL1.3] - Crashes on start-up.
« on: April 07, 2014, 10:47:25 pm »
My apologies. I was under the impression it wouldn't let me use pastebin since it demands you to have made a certain number of posts before you can post links. (I think I actually tried it in the past, but it wouldn't let me, though I figured out that issue on my own.)

It seems like I derped up. Works fine for me now. I think the issue may have been that the program I used to open the config removed the format upon saving. (This time a prompt came up telling me about it, so I just swapped over to notepad and saved it from there instead.)

Thanks for the reply though!

Another question, when I bring up the window for picking water texture (ocean, slow, lava etc.) it won't let me pick anything. Is that a known issue or did I do something wrong with it?

8
Noggit / Re: texture fucked, cant resolve it with noggit
« on: April 07, 2014, 05:00:54 pm »
By chance related to this, might be worth a shot anyways:

Quote from: "Mjollna"
About the "lines" bug, I've tested this and for me it works :

[18:05] <Mjollna> for your broken textures
[18:05] <Mjollna> (the lines problem I mean, not the specular stuff)
[18:05] <Mjollna> you open your adt
[18:05] <Mjollna> in noggit
[18:05] <Mjollna> raise tool
[18:05] <Mjollna> brush size : max
[18:05] <Mjollna> speed : 0
[18:06] <Mjollna> you click once somewhere on your adt
[18:06] <Mjollna> save
[18:06] <Mjollna> test ingame
[18:06] <Mjollna> it should be alright
[18:06] <Mjollna> and to reproduce the bug, it's easy : editing textures on Azeroth instead of a user-created map from scratch

Tested with 279 and latest SDL, same problem, same solution.

9
Noggit / [SOLVED] - [Noggit SDL1.3] - Crashes on start-up.
« on: April 07, 2014, 03:29:41 pm »
Hello. I've been following Noggits development for quite a while, though. This is the first time I make a post.

Edit: I think you already know by the tutorial pack, but my WoW version is 3.3.5a.

I've been using the tutorial pack handed by Steff up till now, but decided to give SDL1.3 a whirl, thinking that it'd be more stable now after a couple of months. Though, I run into this error when I start it:


[paragraph:7ogmww6v]1 - (Noggit.cpp:444): Noggit Studio - 3.166
1 - (Noggit.cpp:250): Using config file.
2 - (errorHandling.h:64): [Error] There was an exception of type "SIGABRT"
"Abnormal termination, such as instigated by the abort function. (Abort.)".
Please excuse the inconvenience. You may want to report this error including the log to the developers.

2 - (StackWalker.cpp:1133): [Error] OS-Version: 6.2.9200 () 0x100-0x1
49 - (StackWalker.cpp:1133): [Error] 002EFA3C (noggit): (filename not available): (function-name not available)
49 - (StackWalker.cpp:1133): [Error] 0029009C (noggit): (filename not available): (function-name not available)
49 - (StackWalker.cpp:1133): [Error] 70D63254 (MSVCR110): (filename not available): abort
49 - (StackWalker.cpp:1133): [Error] 003046C0 (noggit): (filename not available): (function-name not available)
49 - (StackWalker.cpp:1133): [Error] 753294F5 (KERNELBASE): (filename not available): UnhandledExceptionFilter
49 - (StackWalker.cpp:1133): [Error] 774E89E5 (ntdll): (filename not available): LdrSetAppCompatDllRedirectionCallback
49 - (StackWalker.cpp:1133): [Error] 774898C4 (ntdll): (filename not available): RtlInitializeExceptionChain[/paragraph:7ogmww6v]


It does seem to have problems with my OS-version, though I use W8.1. And I know it works for other users here whom uses 8.1?

As I said, I use the tutorial files as pathways (including the two WoW maps for MV and Noggit, as well as my project folder.)

And these are the settings I use:


[paragraph:7ogmww6v]#This is a config file template. To use it rename into noggit.conf and set your options
#Edit this to your WoWFile!!!
#Path = C:WoWModdingClient335aNoggit

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

#Set this to the file where you will import models from (the model viewer log for example :) )
#ImportFile  = C:WoWModdingToolsWoWModelViewer7userSettingslog.txt

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

Don't know if the issue is related to the pathway settings, but I figured I might as well post it. The error said I should hand it over to a dev, so here I am.

Thanks for any help.  ;)
                                   ~Cutsforhugs


EDIT: Silly me, for not looking into the "bad threads" section. It seems to be a similar / identical issue to the pathway crash that the top thread in the section had.

If that's the case, I have a slightly different question: what should my paths look like? Seeing as I use the tutorial folders, and they are in the right place in order to work, I guess I just botched the pathway config somehow. I just don't know how.

Actually, I decided to take a look in my NoggitSDL tutorial version that came in the tutorial pack. The pathways are identical (except for the tutorialproject path, fixed it and it still doesn't work.)

My original Noggit SDL config:

[paragraph:7ogmww6v]#This is a config file template. To use it rename into noggit.conf and set your options
#Edit this to your WoWFile!!!
Path = C:WoWModdingClient335aNoggit

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

#Set this to the file where you will import models from (the model viewer log for example :) )
ImportFile  = C:WoWModdingToolsWoWModelViewer7userSettingslog.txt

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

As you can see, identical.

10
Noggit / RE: Noggit SDL1.3
« on: April 07, 2014, 03:19:10 pm »
Edited, I decided to make a topic in a more proper area instead of listing my problem here.

Hi! Nice to meet everyone.

Pages: [1]