Doesn't properly exports obj file

[AmazingDiamond]

I tried multiple versions, with and without updating libMBIN, and it opens and views fine, but after i save any model the file size is under 1MB and when i try opening it in Blender it shows almonst nothing - just one tringle or floating points. It's like mesh is crumbled into one plane, but even worse.

i have checked the logs, and noticed that at the very end there's "NOT IMPLEMENTED YET" which I suppose appears when it's esporting. This is confirmed by same multiple messages after repeated attempts to save in row and closing. I have watch a youtube guide which the firts version NMSMV_v0.89.4 was used, having exaple that it should work, but when i opening mbin it crashes

[gregkwaste]

Thanks for the report! It is advised to always use the latest version + the updated libmbin version just to make sure there is no inconsistency with previous versions of the game. Can you please tell me which file you tried to export so that I can take a look?

[AmazingDiamond]

literally anything i have tried: walker sentinel, the drone, some spacecraft parts. On a screenshot it's a minotaur from "robots/mech". I must mention that the "NOT IMPLEMENTED YET" part is gone after reinstall it today. But still no use. this is from that mino config and it's OBJ: 1.zip I have opened it thought the notepad and it's look real - a giant string of coordinates, but trying to open it in blender or CAD programm makes it like nothing. Opening other OBJ files from internet work normal on my PC, so i don't even know if the problem is on my end or not.

[gregkwaste]

Thanks for the info. I'll take a closer look once I can and I will let you know. In obj files, lines that start with v are vertex coordinates, while lines that start with f are faces. In blender normally you should be able to see at least some object being imported. Even if its only vertices. But you should see at least a mesh in the scenegraph.

[pixelquarry]

Just chiming in. I ran into the same problem and replaced the libMBIN.dll with the latest version. That solved the decompile error message but did nothing for the OBJ export.

Everything looks fine in NMSMV...

...but the exported mesh looks like this. The vertex count seems unaffected though.

Cheers!

[gregkwaste]

Hello guys,

sorry for my late reply, I found out some time know to update the code base and deal with all the open issues. I cannot reproduce the issue with the obj export and I don't see any introduced change from 0.91.1.

I just tried exporting the astronaut model, the entire dropship_proc.scene and the walker drone as well

Tried to import the exported obj's in Blender and the 3D Viewer and it seems to be working as intended (well the textures are not included but this is expected)

I'll push 0.91.2 in the upcoming days so please keep an eye and let me know if the issue persists. My expectation is that even with 0.91.1 obj export should work as intended.

[pixelquarry]

Hey Greg, no worries, thanks for looking into this.

I did some testing on my own to see if the problem could be on my end. The fact that you can't reproduce the export error seems to confirm my suspicion.

Since Steam allows downloads of older releases of games, I downloaded NMS from before v0.91.1 came out, even tired earlier releases of NMSMV. It either crashed right away or resulted in the same mesh mess.

So I guess the problem is caused on my system. Can you think of anything that might be different between our systems? Version of NMS, NMSMV, libMBIN? I think I'm up to date on all of them. Are there any components in the export process that use system resources outside of NMSMV? Some windows libs that might be different for some reason?

I'll wait for v0.92 and hope for the best.

Cheers

[pixelquarry]

I'm at a loss...

• new PC
• new install of Steam
• new install of NMS
• new download of v0.91.1
• new install of .NET 6.0

"Do you have unpacked game files?" > no > "Open file from .pak" > export as obj > WORKS!

• new download of MBINCompiler_v4,37,0-pre1
• unpack game files

"Open file" > export as obj > Doesn't work "Open file from .pak" > export as obj > Doesn't work (OMG, why? It's the same original game file.) "Update libMBIN" > export as obj > Doesn't work

I have no clue what's going on :(

[pixelquarry]

Would it be possible for you to send me the entire dropship_proc.scene from your test as an obj?

[gregkwaste]

Hey Greg, no worries, thanks for looking into this.

I did some testing on my own to see if the problem could be on my end. The fact that you can't reproduce the export error seems to confirm my suspicion.

Since Steam allows downloads of older releases of games, I downloaded NMS from before v0.91.1 came out, even tired earlier releases of NMSMV. It either crashed right away or resulted in the same mesh mess.

So I guess the problem is caused on my system. Can you think of anything that might be different between our systems? Version of NMS, NMSMV, libMBIN? I think I'm up to date on all of them. Are there any components in the export process that use system resources outside of NMSMV? Some windows libs that might be different for some reason?

I'll wait for v0.92 and hope for the best.

Cheers

Hmmm so you're trying to export from an older game version?

[pixelquarry]

I tried to export from the newest version and when that didn't work I tried some older ones. Just to see if that gives me a different result.

[gregkwaste]

I tried to export from the newest version and when that didn't work I tried some older ones. Just to see if that gives me a different result.

Unfortunately since there are usually minor changes to libMBIN, the NMSMV codebase has to be updated most of the time due to these changes, so unfortunately versions are not (always) backwards compatible. Your best bet is to always use the latest release along with the latest libMBIN either included in the release or an updated version (via the app).

I'll re-export the objs once I got some time just to make sure that it works with the version that I'm planning to release and I'll send them over.

[pixelquarry]

Thank you!

[pixelquarry]

So, I've tried v0.91.2 and got the same results 😔 It has to be something on my end that messes up the exports. If you ever get the chance to export the dropship model again, I'd appreciate a download link.

Cheers

[gregkwaste]

Sorry, for the late response, several bugs have been improved since. Re-open a new issue if problems persist