|
Forum > Noggit
[OLD] changeset 263 (2d448f67eb48)
<< < (5/8) > >>
schlumpf:
--- Quote from: "Mjollna" ---- Importing from a text file works great. However, I couldn't import from wmv's (Wow Model Viewer) log. I configured my config file to indicate where the log is, Noggit finds the log and reads what's inside, but doesn't find the M2. The error in Noggit's log is "It was not in any MPQ.".
If I copy the path in the import.txt and try to import the model it works, so I think the path to the M2 is right.
I use the latest wmv (0.7.0.1 r614 64-bit), which loads my live 4.2.2 files. However, the path/info doesn't seem to have changed between 3.x and 4.x for that particular model. I tried different models, with the same kind of error.
Full Noggit log : http://mjollna.org/docs/misc/wmv_pb_noggit_log.txt
Full wmv log : http://mjollna.org/docs/misc/wmv_pb_wmv_log.txt
Full config file : http://mjollna.org/docs/misc/noggit.conf
Full import.txt (when I then imported the same model successfully) : http://mjollna.org/docs/misc/wmv_pb_noggit_Import.txt
--- End quote ---
As you can see, it does not get the model only but also the logging extra text. That should be stripped away, I guess.
--- Quote ---- I think I also had the "really high camera" problem, but to me it's not mfbo (because the map I had the problem on just has no mfbo at all and never had one).
--- End quote ---
I'm sorry, but the blue foggy thing _is_ MFBO. I don't know why Noggit adds one, but it does. (I probably wrote that code.) When your camera is clipped and you can't fly there: It's MFBO. There is no other mechanic doing that.
--- Quote ---- When I raised terrain on one of my edited maps (I'm currently trying to create my version of a finished ED canyon :) ), some of the saved chunks appeared clearer the next time I opened the map in Noggit, and I could also see that ingame. It looked like the same problem as in 104 (normals ?), so I used the raising brush with full radius at speed 0 to correct it.
--- End quote ---
Yeah, normals are borked. They are most likely also the reason for the EVERYTHING SHINES! problem.
--- Quote ---- I can't open adt saved with 263 with Taliis (sorry, I don't know where I can see in Taliis which version I'm using, if someone has a clue on this... ?). I tried to compare the same adt saved with 104 and 263. The only change I've seen is empty mclq everywhere on the 104 file, and Taliis console mentions "mclq not found", so I don't know if there's a link... ? Vertices/Normals were also different, but I tried to copy/paste some mcvt/mcnr from one 263 file to the 104 one and it didn't seem to have any influence (ie Taliis accepted to open the hex edited file).
--- End quote ---
That is an error on Taliis' side though. MCLQ is not mandatory, therefor we leave it out.
--- Quote ---- It's not much, but some M2 lights/effects don't appear, whereas they do in 104. I noticed that on that particular model I use : worldgenericnightelfpassive doodadslampskalidarstreetlamp02.mdx
Here is one screenshot to show this :
http://mjollna.org/docs/misc/lights.png
--- End quote ---
I don't see what could be causing this. May you save the file in both versions once and make a binary difference of them? The only possibility, I guess, could be in MDDF flags. No idea otherwise.
--- Quote ---Hope that helps... Is it better with one big post like this one or several smaller posts for each issue ?
--- End quote ---
Both help. Do as you like.
-- schlumpf
Mjollna:
Hi :)
--- Quote ---As you can see, it does not get the model only but also the logging extra text. That should be stripped away, I guess.
--- End quote ---
Oh ok, I hadn't noticed the extra text -_-
--- Quote ---I'm sorry, but the blue foggy thing _is_ MFBO. I don't know why Noggit adds one, but it does. (I probably wrote that code.) When your camera is clipped and you can't fly there: It's MFBO. There is no other mechanic doing that.
--- End quote ---
Ok.
I missed the chunk yesterday, I tried to find it on a file where I couldn't find it whatever I tried, but today I tried on another file and I found it quickly... I probably messed up something somewhere.
I've tried a lot of things tonight but in the end, nothing really came out of it, and now I need some sleep... I don't really know what triggers the creation of the chunk, every time I think I get it, I can't re-create it for sure.
--- Quote ---I don't see what could be causing this. May you save the file in both versions once and make a binary difference of them? The only possibility, I guess, could be in MDDF flags. No idea otherwise.
--- End quote ---
I've done that, and MDDF match on both files :
http://mjollna.org/docs/misc/mddf.png
I've tried to look at other chunks, but apart from mcrf/mclq/mcnr they look pretty close.
I forgot to say that yesterday, but although the lights don't show up in 263, a file saved with 263 correctly displays the lights ingame. It's really just when opening a file in the beta that they don't appear.
schlumpf:
--- Quote from: "Mjollna" ---I've tried a lot of things tonight but in the end, nothing really came out of it, and now I need some sleep... I don't really know what triggers the creation of the chunk, every time I think I get it, I can't re-create it for sure.
--- End quote ---
No need for you to check that. I could easily find it, as its only referenced about three times in the whole code.
005540
005701
--- Code: --- // - MFBO ----------------------------------------------
if( Header.flags & 1 )
{
theFile.seek( Header.mfbo + 0x14 );
theFile.read( &fourcc, 4 );
theFile.read( &size, 4 );
assert( fourcc == 'MFBO' );
int16_t mMaximum[9], mMinimum[9];
theFile.read( mMaximum, sizeof( mMaximum ) );
theFile.read( mMinimum, sizeof( mMinimum ) );
static const float xPositions[] = { this->xbase, this->xbase + 266.0f, this->xbase + 533.0f };
static const float yPositions[] = { this->zbase, this->zbase + 266.0f, this->zbase + 533.0f };
for( int y = 0; y < 3; y++ )
{
for( int x = 0; x < 3; x++ )
{
int pos = x + y * 3;
mMinimumValues[pos * 3 + 0] = xPositions[x];
mMinimumValues[pos * 3 + 1] = mMinimum[pos];
mMinimumValues[pos * 3 + 2] = yPositions[y];
mMaximumValues[pos * 3 + 0] = xPositions[x];
mMaximumValues[pos * 3 + 1] = mMaximum[pos];
mMaximumValues[pos * 3 + 2] = yPositions[y];
}
}
}
--- End code ---
--> its not read badly from file, else it would fail at the assertion.
005804
--- Quote ---alcatraz295:src berndlorwald$ grep mMinimumValues *
MapTile.cpp: mMinimumValues[pos * 3 + 0] = xPositions[x];
MapTile.cpp: mMinimumValues[pos * 3 + 1] = mMinimum[pos];
MapTile.cpp: mMinimumValues[pos * 3 + 2] = yPositions[y];
MapTile.cpp: glVertex3f( mMinimumValues[lIndices*3 + 0], mMinimumValues[lIndices*3 + 1], mMinimumValues[lIndices*3 + 2] );
MapTile.cpp: lMFBO_Data[lID++] = mMinimumValues[i * 3 + 1];
MapTile.h: GLfloat mMinimumValues[3*3*3];
--- End quote ---
There is no writing access.
005932
--- Code: --- // MFBO
if( this->mFlags & 1 )
{
size_t chunkSize = sizeof( int16_t ) * 9 * 2;
--- End code ---
It only writes if Flags & 1 is given.
010200
--- Quote ---MapTile.cpp: lTile.mFlags = info.Flags;
MapTile.cpp: if(info.ofsHeightMap != 0 && !(lTile.mFlags & 2)) {
MapTile.cpp: if(info.ofsInfoMask != 0 /*&& !(lTile.mFlags & 2)*/) {
MapTile.cpp: lADTFile.GetPointer<MHDR>( lMHDR_Position + 8 )->flags = mFlags;
MapTile.cpp: lMODF_Data[lID].flags = it->second.mFlags;
MapTile.cpp: lInfo.Flags = tTile.mFlags;
MapTile.cpp: if( this->mFlags & 1 )
--- End quote ---
Problem: mFlags never is written.
010743
--- Code: ---diff -r 52e91fc0a3ed src/MapTile.cpp
--- a/src/MapTile.cpp Wed Sep 21 20:15:40 2011 +0200
+++ b/src/MapTile.cpp Thu Oct 06 01:06:54 2011 +0200
@@ -114,6 +114,8 @@
theFile.read( &Header, sizeof( MHDR ) );
+ mFlags = Header.flags;
+
// - MCIN ----------------------------------------------
theFile.seek( Header.mcin + 0x14 );
--- End code ---
“@Noggit3: Commit: Fixed flags never getting saved in MapTile, resulting in bad MFBO chunks. (randomly)”
That's fixing stuff, live.
--- Quote ---It's really just when opening a file in the beta that they don't appear.
--- End quote ---
Oh, I got you wrong then. Well, its just another stupid rendering bug then. I thought you'd be talking about ingame. My bad. Of course there is no difference in the files then.
Mjollna:
Thanks for your detailed reply and the fixing, it's great ^_^
Fyrion:
This version (263 - 2d448f67eb48) isn't working for me. The following error appears when i am starting it.
http://pastebin.de/19298
Versions from v120_b19 - v120_b22 works fine for me. All drivers are the newest!
The Noggit.conf is exactly the same, as in version b22 (b22 works fine!)
--- Code: ---# This is a config file tamplate. To use it rename into noggit.conf and set your optiones
#Edit this to your WoWFile!!!
Path = D:\Cataclysm2World of Warcraft Public Test
#Edit this to your Project-Directory and uncomment if you want to use it!
ProjectPath = D:NoggitEditor
#Set this to the file where you will impor models from (the modelviewer log for example :) )
ImportFile = D:WMVuserSettingslog.txt
#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=4096
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
|