I've played the demo some time ago, and it does look spot-on as if you're actually there, though some of the visuals look inconsistent at worst. Like for instance the fore and aft Grand Staircases and first-class public areas look a lot more photorealistic than the docks the ship is berthed in the g...

The latest OBJ dump you sent to me had some of the meshes merged, but oh well... From mesh number 58 to 70 everything is labeled Wing_L_58 , that's probably wrong so rename them, please. Also some meshes remain clumped in the middle. You need to rename a dozens of meshnames in the obj file. ( g sub...

I'll keep an eye on that thread: https://zenhax.com/viewtopic.php?f=5&t=8872 If there's no progress within one month maybe I'll give it another try next year. btw: most submesh positions of the Yaris in the zip I uploaded are correct without using a skeleton but guess I'd need to apply some rotatio...

Thing is, if you had told you opened the same thread on zenhax it would have spared me tons of lifetime. That's a matter of respect, too. As simple as this. Seems you don't know about cross-posting, do you? " 2. It wastes the time of those trying to help. " "Please don't cross-post questions on mul...

Not nice, huckleberrypie, to let people work in parallel, on zenhax and here on xentax. :roll: I'll stop my investigations. Oh, sorry about that mate, I didn't mean to disappoint you on this one. If you no longer feel like working on this one, fine, but please, I really didn't mean to burst your bu...

In regards to part positions, Szkaradek123 over at Zenhax mentioned about the NoHe node containing the necessary bone/skeleton stuff:
https://zenhax.com/viewtopic.php?f=5&t=8872

Looks straightforward but tbh I have no idea on how to open the stuff in these RIFFs. I can open the file in a RIFF viewer but, well...
https://www73.zippyshare.com/v/AauPpLjC/file.html

Problem is that some NoHe names don't seem to be connected to a mesh because they are "joints" such as J_Bumper_BL for example. I really don't have the patience to crawl through that damned hierarchy to decide how to assign the meshes to the "real" mesh names. :D As for example D_Exhaust, D_Exhaust...

It's Riffview, but it misses the 2nd half of the nodes, too bad. So I decided to get a C# project from the inet, RiffparserDemo which allowed me to create some position2node list manually. There's some things I don't understand so far, so for example J_Bumper_BL_10, J_Bumper_BR_11, J_Bumper_FL_12, ...

btw, we'd need a decent Riff viewer with the ability to export the hierarchy. The one I have stops at node 32 for some unkn reason: 0. Root 1. D_Main 2. Piston_FR 3. Piston_RR 4. D_Exhaust 5. D_Exhaust_Flash 6. Exhaust 7. HUD_INT 8. J_Boot_L 9. J_Boot_R 10. J_Bumper_BL 11. J_Bumper_BR 12. J_Bumper_...

Yeah I know that. I was actually referring to the Make_obj project with C source code. The Make_obj project is not blender specific, it creates wavefront obj outputs which can be read by most 3D apps. (But it wouldn't help you that much if you don't know 'C'.) I see, so it's a standalone applicatio...

shakotay2 wrote:

huckleberrypie wrote:I presume the Makeobj thingy you mentioned is for Blender, yes?

Output is (one) wavefront .obj with submeshes (see zip file) so any 3D app should do.

Yeah I know that. I was actually referring to the Make_obj project with C source code.

Anyways, here's the zip with uvs contained: https://www7.zippyshare.com/v/3yF3IYqF/file.html Some uvs may need some scaling (1.5?) but the selected one in the picture obviously not: Toyota_Yaris-P3D-uvs.png I presume the Makeobj thingy you mentioned is for Blender, yes? One thing though: Could you ...

I do hope someone would be kind enough to do a script which can at least parse these models completely. yeah, maybe. Me, I'm finished with this: https://www63.zippyshare.com/v/Deke91Lr/file.html Toyota_Yaris-P3D-undone.png Too tired to solve stupid naming puzzles like this one. :roll: Keep in mind ...

I don't know - I searched for "NodsNoHe" which is contained 67 times. There's also MeLiMesh (43x), GeLiGeom (71), SGLiSuGe (71) but guess that's different things. Maybe I should use PA__Head, SCENE___ENDI, PCPhHe and something else for the missing 4 nodes? There's numbers for "NodsNoHe" but they se...