Re: 3D Model Researcher - extract 3D models with Python
Posted: Thu Dec 27, 2018 9:16 pm
where am i wrong ?? Why it cant be
https://drive.google.com/drive/u/0/fold ... C?ogsrc=32
https://drive.google.com/drive/u/0/fold ... C?ogsrc=32
Game Research Forum
https://forum.xentax.com/
Thank you! Bug fixed. Other byte reading errors were also fixed.Beedy wrote:There is a bug in Xp version of Model Researcher v2.4.2. My model is big endian and vertices is half-float and faces is short. Trying to toggle endian there is no effect and values doesn't change. Setting type to float endian change works properly. I don't know how it works in latest version v2.5 because win7/win8/win10 version of Model Researher doest't work with Wine on Mac.
Edit. Endian change works with faces but it doesn't work with half-float vertices.
Thank you! My last question is about uv’s. I can’t get right values with type Short_sign in MR Xp version. Is short_sign same type than WordUV or Short All in Hex2Obj which I can get right values for Uvs?Lazov wrote:I updated the version for Windows XP.
CheersLazov wrote:adroduke
It is probably better to write about this in this topic, attaching the model file:
viewforum.php?f=16
They do not show up correctly on Windows 10 either. I tried for the last 2 hours to get the UVs to show up correctly on that one and it doesn't seem like the correct format for those UVs is supported yet.Beedy wrote:Thank you! My last question is about uv’s. I can’t get right values with type Short_sign in MR Xp version. Is short_sign same type than WordUV or Short All in Hex2Obj which I can get right values for Uvs?Lazov wrote:I updated the version for Windows XP.
My model information
Big Endian
Vertices:
Offset: 0x800
Type: Half-float
Count: 692
Padding 26
Faces: 0x5e80
Count 1536
Type: Short
Format: Tri Strip FF
UVs
Offset: should be 0x810 (Hex2Obj: FVFsize 32, UV pos 16)
Count: 692
Padding: 28
First uv values should be vt 0.753769 0.968872 (Hex2Obj) but I got vt -0,4992 -0,0623 in MR.
I tried to set Vertices type short_sign in MR and ShortALL in Hex2Obj and got same values for vertices. So I think WordUV and Short_sign is same.
What is wrong with uvs?
Model in attachmet if you want to take a look.
UpdateBeedy wrote:Thank you! My last question is about uv’s. I can’t get right values with type Short_sign in MR Xp version. Is short_sign same type than WordUV or Short All in Hex2Obj which I can get right values for Uvs?Lazov wrote:I updated the version for Windows XP.
First uv values should be vt 0.753769 0.968872 (Hex2Obj) but I got vt -0,4992 -0,0623 in MR.
I tried to set Vertices type short_sign in MR and ShortALL in Hex2Obj and got same values for vertices. So I think WordUV and Short_sign is same.
Thank you Lazov! This is just what I need for Skate 1, 2 and 3 world/ level models. They use that type.Lazov wrote:UpdateBeedy wrote:Thank you! My last question is about uv’s. I can’t get right values with type Short_sign in MR Xp version. Is short_sign same type than WordUV or Short All in Hex2Obj which I can get right values for Uvs?Lazov wrote:I updated the version for Windows XP.
First uv values should be vt 0.753769 0.968872 (Hex2Obj) but I got vt -0,4992 -0,0623 in MR.
I tried to set Vertices type short_sign in MR and ShortALL in Hex2Obj and got same values for vertices. So I think WordUV and Short_sign is same.
Apparently, unsigned Short is used in Hex2Obj when reading textural coordinates. I added a new type to the block UVs - Short. Thanks for finding bugs and flaws!
New versions are available on the site. The update for the Pro version will be released later.
Thanks for the quick response. This is a great tool.Lazov wrote:
Update
Apparently, unsigned Short is used in Hex2Obj when reading textural coordinates. I added a new type to the block UVs - Short. Thanks for finding bugs and flaws!
New versions are available on the site. The update for the Pro version will be released later.