Hello everyone, I would like to ask for help in extracting the 3D models (*.mcms) into any other format. The game was created using the Mascot Capsule EruptionST Engine. I’ve included a *.mcts file, which is the texture file, in case anyone wants to take a look. I would be very grateful if you could help me.

sample files.zip

Edited January 28, 20251 yr by Codwai

your *.mcms file is written in blocks. I made a test plugin that opens models as a point cloud. fmt_mcms.py

*(faces are not simple, need to look into them in more detail)

Edited January 9, 20251 yr by Durik256

1 hour ago, Durik256 said:

by keyword POSX you can find all meshes, step back 8 bytes and you will get the number of vertices. stride 8 bytes, vertices as signed short

there are also many textures

example of some meshes (point cloud):

Hello, thank you for the response. As I don’t have much knowledge in reverse engineering and coding, I’m having trouble understanding how to search for the keyword ‘POSX’ and work with the vertices. If you could guide me more on how to start or suggest any tools, I would greatly appreciate it!

I used the hex viewer HxD, and noesis (python) for quick viewing. You can go to the tutorial topic of this forum to learn more about reverse. Use for example my meshFinder (still in testing), or hex2obj from Shakotay, or ModelResearcher.exe etc.)

Edited January 9, 20251 yr by Durik256

14 hours ago, Durik256 said:

by keyword POSX you can find all meshes, step back 8 bytes and you will get the number of vertices. stride 8 bytes, vertices as signed short

The files from the attached "sample files.zip" do not contain the "POSX" characters.

Did you use other files from the game?

(I did not downloaded the game.)

2 hours ago, Karpati said:

do not contain the "POSX"

You're right. My mistake. I wrote in the wrong topic.

On 1/8/2025 at 12:49 AM, Codwai said:

the 3D models (*.mcms)

there was a mistake, I wrote in the wrong topic. I corrected the first message, but my subsequent answers remained relevant

Edited January 9, 20251 yr by Durik256

9 hours ago, Durik256 said:

there was a mistake, I wrote in the wrong topic. I corrected the first message, but my subsequent answers remained relevant

I understand, thank you for your help, man