Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import / export of hyrachia, object and texture names #265

Open
JohannesSAUT opened this issue Feb 15, 2024 · 1 comment
Open

Import / export of hyrachia, object and texture names #265

JohannesSAUT opened this issue Feb 15, 2024 · 1 comment

Comments

@JohannesSAUT
Copy link

JohannesSAUT commented Feb 15, 2024

First of all, thank you for someone caring about this old game engine.

However, I have a problem.
The textures are constantly renamed when exporting.
This doesn't matter for Blender.
In games, all points “.” are new objects.
The driver entry “normalmappet.fx” may be exported as “normalmappet.fx.00X”.
Would it be possible to stop this?

W3D works with Planes.
These are simple areas that show the game where something is limited. Be it for entering, climbing over, transitioning from the landscape to the model, as an obstacle, or in special cases, what can be undercut. These areas should be invisible.

A Hyrachian model needs no bones and no amature.
However the filter returns an error?

An amature is automatically created during import.
For buildings without animation, completely pointless.
In addition, some functions do not work with buildings.

I would ask you to assign names to the objects in the W3D options and to strictly adopt them.
Blender is constantly evolving. This is brilliant for filmmakers.
For us modders, that means spending hours tricking Blender and naming objects the way we need them.
A field in the W3D Proberties where you can enter the identifier that will be published would be extremely helpful.

Should I have missed something?
Then I politely apologize.
Where do I need to check the box or change the name?

Thank you, Johannes

@Tarcontar
Copy link
Collaborator

Tarcontar commented Sep 27, 2024

Hi,

  • your first issue should be solved by starting up a clean session of blender when importing models. If you already have imported various models then the renmaing might happen.

  • Actually for the Plugin a hierarchy needs bones since various modles would not be able to be imported otherwise.

  • Same as the point above.

  • I dont get that point really. What are you trying to accomplish?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants