NFS No Limits

[Bigchillghost]

I couldn't get better results

Well, I couldn't see the images posted by GreenTrafficLight earlier. But from that screenshot where AMR interpretated the data as "char", you can clearly see that the square sum (the value on the right of the arrow) of every vector approximately equals to 1.0 within the acceptable error range. That's the most convincing evidence that the data type must be "char", or signed byte.

The error between using the formula

Code: Select all

n1 = vertexBuffer.readByte() / 127;

and

Code: Select all

n1 = vertexBuffer.readByte() * 2 / 255; // == vertexBuffer.readByte() / (255 / 2) == vertexBuffer.readByte() / 127.5

is really insignificant and you can even use 128 as the divisor if you'd like to. So from my point of view this problem isn't actually related to the convertion.

[GreenTrafficLight]

I wrote the script using the BMesh functions this time (well, to be honest, I copy-pasted since DGIorio did already something perfect), but i'm getting the error "Found the same (BMVert) used multiple times" (which can be fixed with a try/except). This error concern some mesh like mesh_glass_windows_a_lod01 (bmw_m3_gtr), but the mesh is still generated and doesn't have any problems. So I don't know if it's really a big issue.



The problem is, I feel that using these functions has more chance for blender to crash (like sometimes, using the script more than 3 times will crash, and sometimes, it will be fine). but the good news is, the normals are actually applied.
(Top is from Advanced Mesh Reaper, Bottom is from the script)



I think it's a problem related to Blender and not the convertion itself.
(Auto-smooth gives a different result, so It doesn't work as a fix)



P.S : The script is not finished at 100%

[Fiammanera628]

And for the UV coordinates? There are any news?

[GreenTrafficLight]

And for the UV coordinates? There are any news?

Some vertex buffer have different format, for example, at stride 24, some start at 12 and others start at 20.

And sadly turn out that the normals is kind of right, but also broken, the traffic_dodge_charger has a broken normal on the right side and selecting it in edit mode fix it, but also break all the other normals (that apply to all model)

(left is Advanced Mesh Reaper, right is from the script)


(It seems that normal are the right one, it must be something to fix in the blender script)


(Entering a mesh in edit mode break all the normals)


Man, Blender is so weird to work it, I kinda wish there was a way to attach the zstandard module to a noesis script (which I tried but didn't work)

[zimex25]

I wrote the script using the BMesh functions this time (well, to be honest, I copy-pasted since DGIorio did already something perfect), but i'm getting the error "Found the same (BMVert) used multiple times" (which can be fixed with a try/except). This error concern some mesh like mesh_glass_windows_a_lod01 (bmw_m3_gtr), but the mesh is still generated and doesn't have any problems. So I don't know if it's really a big issue.



The problem is, I feel that using these functions has more chance for blender to crash (like sometimes, using the script more than 3 times will crash, and sometimes, it will be fine). but the good news is, the normals are actually applied.
(Top is from Advanced Mesh Reaper, Bottom is from the script)



I think it's a problem related to Blender and not the convertion itself.
(Auto-smooth gives a different result, so It doesn't work as a fix)



P.S : The script is not finished at 100%

Isn't too much normals? AE86 rear fenders doesn't look good.
Edit:
F355 also looking "plastic". Rear bumper of E46 looking nice but not perfect. Idk maybe it's problem only in my.
https://ibb.co/RQLgdVv
https://ibb.co/TbMmb9r

[Fiammanera628]

And for the UV coordinates? There are any news?

Some vertex buffer have different format, for example, at stride 24, some start at 12 and others start at 20.

And sadly turn out that the normals is kind of right, but also broken, the traffic_dodge_charger has a broken normal on the right side and selecting it in edit mode fix it, but also break all the other normals (that apply to all model)

(left is Advanced Mesh Reaper, right is from the script)


(It seems that normal are the right one, it must be something to fix in the blender script)


(Entering a mesh in edit mode break all the normals)


Man, Blender is so weird to work it, I kinda wish there was a way to attach the zstandard module to a noesis script (which I tried but didn't work)

I extracted the whole game, if is needed, I can paste the links

[shakotay2]

the traffic_dodge_charger has a broken normal on the right side and selecting it in edit mode fix it, but also break all the other normals (that apply to all model)

well, I know you like it "perfect", so dunno if this helps: I exported the lod00 selection only as a wavefront obj file, deleted all meshes then re-imported the obj.

For me it looks fine (not perfect, though ).

(But I have to admit that I didn't understand what you meant exactly with: "(Entering a mesh in edit mode break all the normals)"
for your latest picture. The surface not to be perfectly smooth? Or those darker and brighter Areas?)

edit: well, I see, when rotating the reimported lod00 model around and around, it doesn't look perfect. (But for me it's ok.)

[GreenTrafficLight]

well, I know you like it "perfect"

Yeah, but the reason why I think normals are important is because people will probably use these models in mods, and I think broken normals will change a lot how the model will look like in-game. (But I admit I would have liked to ignore this problem )

(But I have to admit that I didn't understand what you meant exactly with: "(Entering a mesh in edit mode break all the normals)"
for your latest picture. The surface not to be perfectly smooth?)

Yep, the surface isn't smooth since it's changed when you enter the selected object in edit mode.

(What the mesh look like before you enter in edit mode)


(What the mesh look like after you enter in edit mode, notice the darker faces that appeared)


I think it related to the fact that the mesh have duplicate vertex that aren't connected (which makes Blender to recalculate the normals). Sadly, merging the vertices doesn't solve the problem.

[shakotay2]

the mesh have duplicate vertex that aren't connected (which makes Blender to recalculate the normals).

Oh, well. I totally forgot about that! I can't believe that there were 2556 doubles in the lod00 I mentioned before, so removing doubles leads to 5431 -2556 = 2875 remaining vertices. Unbelievable.

Even better, newer blender version have the merging by distance feature now, surprise.

[GreenTrafficLight]

Welp, I hate myself, turn out that fixing this problem is really simple (man, I've been on this for three days and tested everything except this), thank to this code

I just had to remplace

Code: Select all

normals.append([n1,n2,n3])

with

Code: Select all

normals.append(Vector((n1,n2,n3)).normalized())

And now, there isn't any problem, also the normals aren't reset when you go into edit mode.

(the left is the one from Advanced Mesh Reaper, just saying)




(I hope I'm not wrong this time , this is probably the only best solution that I have found)

Still, there are problems like, sometimes the car_decal_placement_shell crash Blender when you edit it. And plenty of things that I still need to add.

[Fiammanera628]

Hello,

I noticed that there are also many .sb files, in seperate folders (like Bodykits), I think there are prefabs, but prefabs for what? Idk if there fits into the 3d models but my guess is of yes.

In chase, I attached an example here.

[zimex25]

Hello,

I noticed that there are also many .sb files, in seperate folders (like Bodykits), I think there are prefabs, but prefabs for what? Idk if there fits into the 3d models but my guess is of yes.

In chase, I attached an example here.

.sb files is scripts in game like gamemodes, physcic, customize info etc. In my view is unnecessary files. The most importat with models and textures is sb3d and sba.

[zimex25]

Need For Speed No Limits have different textures in different devices. Using script by Bigchillghost I can ONLY (from my version in mobile phone) extract textures with alpha channel but textures from Iphone looking like diffrent format.
Here is samples from Porsche 911 (991) GT3 R.S:
https://www.mediafire.com/file/6rtnl5ah ... 1.rar/file

[Fiammanera628]

.sb files is scripts in game like gamemodes, physcic, customize info etc. In my view is unnecessary files. The most importat with models and textures is sb3d and sba.

Ah ok, thank you for the clarifications

[zimex25]

Welp, I hate myself, turn out that fixing this problem is really simple (man, I've been on this for three days and tested everything except this), thank to this code

I just had to remplace

Code: Select all

normals.append([n1,n2,n3])

with

Code: Select all

normals.append(Vector((n1,n2,n3)).normalized())

And now, there isn't any problem, also the normals aren't reset when you go into edit mode.

(the left is the one from Advanced Mesh Reaper, just saying)




(I hope I'm not wrong this time , this is probably the only best solution that I have found)

Still, there are problems like, sometimes the car_decal_placement_shell crash Blender when you edit it. And plenty of things that I still need to add.

Any progress of UV Mapping?