Hello ac-web,I have my nogg-it setup as usual . . .
Quote from: "=┤Samibotss├="Hello ac-web,I have my nogg-it setup as usual . . .I'm sorry, but really? Ac-web? Talk about no effort in the copy/paste.Also when will we stop calling it Nogg-It? It's not called Nogg-It.
"Nogg-It? It's not called Nogg-It" XD,you wrote the same names
Quote from: "=┤Samibotss├=""Nogg-It? It's not called Nogg-It" XD,you wrote the same namesUh... wut? You make no sense.Anyway, make sure you have your map.dbc and the custom adts in your client.Also you set your project path to a file name. o_O It wants a folder name.
Blunt assumption, it's the area outside of defined areas (0x0, so to speak) and are caused by missing sky and skybox data.
You got a reason for the problem described. Is not it logical that a problem can be fixed by eliminating the reason!?
Quote from: "Skarn"You got a reason for the problem described. Is not it logical that a problem can be fixed by eliminating the reason!?But here really is your answer .I personaly never have Light.dbc in DBFilesClient or in patches in my Noggit's Data folder. Simply because I hate how light settings behave in noggit and how they tend to obscure my vision a little bit. Yes, I know, I can turn fog off (and I keep having it off all the time), but still, those lighting effects are just a nuisance for me while working.So, try to get rid of your Light.dbc. Keep it in client's MPQ patch, but don't put it into data used by Noggit. We shall see if it helps.
*facepalm*Do you think that Noggit doesn't open and use blizzlike Light.dbc from blizzlike MPQs when there is no edited version in your custom patch? In that case you wouldn't be able to even open ANY blizzliker content in Noggit.