War3 Model Tuner v1.2.7.2

[Villagerino]

So many useful functions, need to check it out!

If you'd like a command added, comment.

I'm very glad you're open for suggestions!

That would be nice to have an option for a list of animations to work with visibility of a certain Geoset, e.g.:
300: 1
1536: 0
2558: 1
4800: 1
A full list from the beginning till the end because Magos makes it shorter and you have to write things by hand
(Usually I use a workaround - to get the list I copy a certain Geoset with its visibility via RMS and then open it in Magos and get its full sequence list.)

It is also hard for Magos to find a certain Geoset Animation, while you can right-click on a Geoset and it's position and also its Material layer will get highlighted, the Geoset Animations won't. If there's a way to open a model after you opened it in Magos, get the same numbers and see a list with what Geoset Animations refer to what Geosets? Or could this me done in Magos? At least people like me and Vinz sometimes suffer from this as you can have like 20 geoset animations in one model, eh.

Huge thanks in advance!

 

[stan0033]

So many useful functions, need to check it out!

and more to come

 

[Villagerino]

Special thanks for the function with normals, I think many will be very happy

Tested the stuff: seems that recalculation does split normals

Spoiler

This function is just top notch, I've never seen something easier for editing the visibilities, great work

Spoiler

It's very handsome that you highlight the geosets, here I only could wish to make the viewer have a bigger scale:

Spoiler

Because huge portrait backgrounds or other big stuff will limit the scaling.

I also wanted to draw attention to the selection of Geosets:

Spoiler

When you want to see something from behind, in this case the back of the head, the viewer resets the camera angle.

Another UI issue is that you cannot see the full Node list when you open the full list of functions:

Spoiler

When you run some of the functions the only way to get back to the full Node list is to use (scroll) your mouse wheel.

In the Textures tab it's hard to track what is what:

Spoiler

Seems that all IDs are set to 0 and you don't know what Material is based on what texture.

There's a sweet function that deletes duplicate Geo Animations:

I wanted to find a function that deletes duplicate Geosets. Am I missing it? If not, when added we can do without running MdlVis or dragging stuff into the MDLX Optimizer

Probably a bug: 'Check for errors' function in the Inspector tab makes the app crash.

I'll keep looking through the other stuff when I have time, I hope that my feedback will help you

 

[Kyrbi0]

I don't quite understand it, but if Villagerino likes it I'm downloading it just in case I need it. ^_^

 

[stan0033]

I don't quite understand it, but if Villagerino likes it I'm downloading it just in case I need it. ^_^

If you understand warcraft 3 models and the editor of magos you would understand this tool. Like any other experienced modeler on this site.

 

[Villagerino]

Love the new stuff in 0.8 and 0.9, especially removing overlapping faces (I believe they are triangles ), work with normals (gonna check this highly useful thing when have time ) and set all geo animations as one specific (helps setting the visibility much, much faster in simpler models - using this in Retera), good job, thanks for your effort

 

[Retera]

Since this is using Magos code from 2008, although I haven't spent a lot of time looking into all the features of this tool yet and I'm just adding a reminder in passing, are you able to confirm if this has the same bugs as other Magos based things such as:

• Changing the name of "length" to "width" and vice versa when opening MDX and saving as MDL
• Sometimes causing light intensity to bounce to an infinite value in some cases (maybe)
• Issues when reading certain models with multiple different TVertices (UVAS) chunks on the same surface. (Volcano spell effect destructable model, Cliff Cave doodad, etc)
• Flipping (or failing to flip) the RGB versus BGR of animated color data (geoset animations)

I'm just mentioning this because in my case, I don't think that I would entrust my work to the Magos War3ModelEditor program typically due to issues like these if I was working on a model, because it would be constraining the parsing and handling of the file to have bugs from 16 years ago that generally weren't fixed during that time.

If you want to convert MDX<->MDL and back to look for errors in the Magos code and perhaps fix that code, one good way to do this would be to use the official Blizzard code for the conversion process. That way, every MDX is guaranteed to create a fully equivalent MDL that will reproducibly generate the same MDX when converted back. Because I already had the official converter available to me from 2004 onwards, by the time 2012 rolled around and I wrote my own custom software for processing models and converting and such, I tended to build my code to expect .mdl extension files to be in the Blizzard format instead of the Magos format. Ideally, there should not be two formats. "Length" should only have one meaning, etc. Until these kind of bugs are fixed, I wouldn't personally write software using Magos's code knowing how many issues it has. But, obviously if you're okay with a certain lower standard and Magos code generating various errors or inconsistencies in files, sometimes it's possible to live that "don't know, don't care" lifestyle and use files that are "good enough" even if they have problems.

 

[stan0033]

@Retera

I knew an older library would have bugs, I didn't know what they are, someone had to tell me.

• Yes, i saw now that loading MDX file (not for mdl) swaps emitter2's Width and Length if they are static.
• thats why there is clamp attentuations in the app. You mean the library saves as that? That "maybe" would mean it happens in rare cases for unknown reasons.
• i dont know what "having multiple texture coordinate chunks on the same surface" mean. Sounds like this shouldnt be valid as there is one texture coordinate per vertex. Do you mean that the list of texture coordinats in the file is longer than the other lists, before combining the lists into vertices? no wait, that would throw an error... i dont know
• I believe that flipping of RGB is done by the developer not that library? the color is initially normalized BGR. So far i havent had issues with colors

Dont make is sound worse than it is, the inconsistensies are not that much.

Kinda suspicious that you "always" had access to official Blizzard code. Are you an ex employee or have direct relations to Blizzard?

 

[Retera]

Dont make is sound worse than it is, the inconsistensies are not that much.

I simply do not want any inconsistencies. Whether that is "worse than it is" or not is a matter of personal preference. There is not anything that would validate my opinions, since they are only opinions, but I'm also not certain that anything would make them invalid. (Nevertheless I thought it might be worthwhile to mention the technological issues, in case you have access to fixing them or if it might motivate you to use a newer library.)

this shouldnt be valid as there is one texture coordinate per vertex.

My definition of what is valid and what is not is something I try to only base on the game contents. To that end, some models have multiple texture coordinates per vertex. The Volcano and the Cliff Cave are examples of this. The volcano even includes independent moving surface texture animation applied to the different texture coordinates independently, but all on the same vertex. But as you have pointed out, caring about that could be considered something that sounds "worse than it is," since any model author could simply declare, "I shall not care about the Volcano ability art nor the power to modify it!" and then using Magos technology is great and fine.

Kinda suspicious that you "always" had access to official Blizzard code. Are you an ex employee or have direct relations to Blizzard?

I am not. Anyone can access this. A hacker named YobGul created a basic GUI app that converted between MDX and MDL using some War3Beta DLLs and published it, probably on wc3c back in the day. When I was a small child, someone copied this YobGul file converter tool onto my computer and I played with it offline even before having access to the internet. So this is a matter of random circumstance and not a matter of direct relations.

However, a bunch of MDX/MDL tools were included in the recent Reforged Debug leaks, so I also mentioned it because I would imagine you might be able to use those tools in a manner similar to the YobGul converter.

 

[Power]

Keep up the good work! Your program is amazing!

Are you planning on adding more options? such as Recalculate Normals ? (Maybe is there and i missed it)

 

[stan0033]

Are you planning on adding more options?

yes, on request and if i can achieve it

such as Recalculate Normals ? (Maybe is there and i missed it)

there is average and negate normals for now

 

[Jaccouille]

Hello, I tried to launch this application but I got the following error message :
"To run this application, you must install .NET. Would you like to download it now?"
When I click yes, nothing happens.
From what I understand, I need to install a .NET runtime that I can manually download here: Download .NET Framework | Free official downloads

But I don't know which one I need. I tried 3.5 SP1, but nothing happened when I tried to run it (as admin, in compatibility mode...).

 

[stan0033]

Hello, I tried to launch this application but I got the following error message :
"To run this application, you must install .NET. Would you like to download it now?"
When I click yes, nothing happens.
From what I understand, I need to install a .NET runtime that I can manually download here: Download .NET Framework | Free official downloads

But I don't know which one I need. I tried 3.5 SP1, but nothing happened when I tried to run it (as admin, in compatibility mode...).

5.0

 

[Villagerino]

new command - Spread overlapping vertices

new command - edit visibility for ALL in sequence.... (useful for example if you want to make the whole model invisible at the end of 'Death' sequence)

 

[Greedy Procrastinator]

Seems like an useful tool in description, I endorse stuff that implements quality of life changes or adapt old software. Going to try to use it for my future stuff.

 

[Power]

You metntioned that you can add features by request, any chance you can add a merge between bones and helpers?

 

[stan0033]

You metntioned that you can add features by request, any chance you can add a merge between bones and helpers?

yes, there is already merge for bone-bone, but i could add that.
As far as the other command 'merge similar bones' im working on it.

what do you want to do in merging process with transformations ? merge, erase, overwrite ?
What to do in case of parent-child relationships and conflicts ? merge, leave?

 

[Power]

You can drop me a personal message and i can give you some examples thanks for responding this quick! im a big fan of your tool!

 

[stan0033]

You can drop me a personal message and i can give you some examples thanks for responding this quick! im a big fan of your tool!

there is no conversation button on your profile

 

[Power]

Same on yours i cant reach your profile. henry5848 my discord.

 

[Villagerino]

Like this 'node inspection' thing

 

[Kyrbi0]

OK so it's a model editing program; nice. This begs the question, though: what sets this apart from Magos, MDLvis, or either of the RMS's? What is the use-case, and/or what deficiency in the others are you covering for with your work here?

/edit/ To be clear, this isn't an accusation or a negative comment. I'm honestly curious. (personally, I use Magos for a lot, but MDLvis has better controls & UVWrapping, while RMS does all that + can import animation sets + other stuff. So they have different functionalities, reasons people might want to use one over the other).

 

[stan0033]

OK so it's a model editing program; nice.

I don't like your dismissive tone

This begs the question, though: what sets this apart from Magos, MDLvis, or either of the RMS's? What is the use-case, and/or what deficiency in the others are you covering for with your work here?

/edit/ To be clear, this isn't an accusation or a negative comment. I'm honestly curious. (personally, I use Magos for a lot, but MDLvis has better controls & UVWrapping, while RMS does all that + can import animation sets + other stuff. So they have different functionalities, reasons people might want to use one over the other).

if you are so curious then you should make the comparisons by yourself by inspecting all the description and trying the app instead of expecting information to be hand-fed to you.

 

[stan0033]

You are responsible for documenting and explaining the functions of your program.

1. There is written explanation of features, screenshots and videos, and a changelog. Plenty already. Functions inside have tooltips and there is 'help' menu
2. Your 'poor' rating is definitely not a fair reflection of the effort put into this project
3. It's not your job to intervene in other conversations.

You are the one having a dismissive and quite gross tone.

I am not dismissive or gross, I am addressing his lack of effort

 

[Kyrbi0]

I don't like your dismissive tone

I'm sorry if my initial post seemed dismissive; I tried to edit in a disclaimer to soften it.

You have done a lot of documentation already, and I was essentially asking you to compare-contrast with other programs, to 'sell me' on this one. If you don't want to, that's fine. If so, it's nothing personal, but I'll probably not have the time to check it out myself (honestly still waiting to dig into RMS & I've known about that one for years, lol), so I wish you luck.