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 ...

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 "NodsNo...

shakotay2 wrote:the positioning problem seems to be solved, but my current problem is
there's 71 nodes but I've got 67 names only

movingTheDoor.png

Did you take a look at similarly-sized nodes though? I bet some of them may have been named crypticly or not at all.

Can you export any infos from Riffpad, or does it create a logfile? I'm too lazy guessing those positon offsets from the P3D file: # 0. 2a 6a 6a , NodsNoHeX, Root # 1. b6 69 6a , NodsNoHeZ, D_Main # 2. cc 78 2 , NodsNoHe^, Piston_FR 0.967096 0.028186 -0.252846 -0.027130 0.999603 0.007665 0.252961 -...

Great, now all we need is a maxscript to automate this. Doing it in 'C' is easier, imho. Maybe in the Make_obj project, but the positions of the parts must be corrected: Toyota_Yaris-P3D-all.png Whichever is more convenient lol. I can presume that some of the nodes do contain pivot positions and th...

Great, now all we need is a maxscript to automate this. I am glad that Kylotonn didn't over-engineer things and relied on a familiar file structure. Heck, you could end up writing an exporter and somehow inject custom cars to the game.

I know I've already started a thread about this a while back, but that was when I attempted to use Ninja Ripper on the game in vain. Turns out that aluigi wrote a script for WRC 7's PKG file formats and that using it reveals a surprisingly good amount of content, all conveniently labelled. That bein...

Anyone?