Newest EDM Model Tools

Can I just say, wow thank you for making these plugins into a nice clean installer? I decided I'd take another look at them and it looks like they're being updated almost daily and in a very efficient manner. To whomever is responsible, thank you! I like the direction this is going.

They are compiled on a daily basis. However that does not mean that there are changes

Do you need to remove the old plugins before installing the new ones?

They'll overwrite, dude. Shouldn't matter.

I would uninstall and reinstall. Since its a proper install package, Windows might get confused. ie: two entries in the add/ remove programs, but only one set of plugins actually installed

Ah ok. Looked like a self-extracting archive to me.

Ah ok. Looked like a self-extracting archive to me.

It creates an entry in the "uninstall a program" field. Im just not sure what happens if you install another version if it updates it, adds a new value, or what. I dont want to test so I would say to be safe, uninstall old and install new

3D Studio Max 2013 (and 2012)

Hi,

Is it possible to get a version of these plugins compiled for 3D Studio Max 2013 (I've searched and not seen anything mentioned) - the current installer only knows about versions up to 2011 - as listed in the oft-updated first post.

I have 2013 64-bit, although I dare say people may have 2012 and need an installer that caters to that too ?

Martin...

2012-13 support would be fantastic, as there are some great new features in both that I would love to have, but the plugins only support as high as 2011 x64.

Can we get some kind of support for all-white textured models? Something where we can limit the amount of bluish gloss around the aircraft? Either that or allow exportation to EDM without needing to apply the 'Make Cool' material effect to it in order for it to export correctly.

Edit: Just read Q/A #5. Going to give that a try real quick.

Edit2: Disregard above, #5 worked. Thanks!

Edit: Just read Q/A #5. Going to give that a try real quick.

 

Edit2: Disregard above, #5 worked. Thanks!

:)

Edit: I figured it out, and answered my own questions below for others to search.

I'm having trouble getting textures to show in ModViewer.

1. Use the textures' original name!
   
2. What format should the textures be? / BMP and DDS work
   
3. Textures should go in the 'TempTextures' folder within ModViewer's install path? / Yes
   
4. For the textures to show, do all associated textures need to be in the folder? / Yes, otherwise you get the missing texture over everything. Even a texture showing properly will get plasterd.
   
5. Does it require the 'Description.lua' file? / No
   
6. Do I need an *.EDM model in the ModViwer's install path somewhere? / No
   

:) got them all right. Except what do you mean by the first? I often export files and rename them later and it always works

I meant use the original name the *.EDM is calling, when viewing them in the program.

ohhhh you meant use the original texture name. gotcha gotcha. thought you meant use the original model name. My bad. Brain fart

haha, no problem.

Hey LuckyBob, just a small remark on newer MVs:

Arg value slider give only minus/plus 0.999 "output" values with maximum left/right moves on the slider line while the predetermined max values are OK: minus/plus 1.00

You should correct it...

Well, if i change manually the "predetermined max values" to minus/plus 1.001 then the "output" will correct: minus/plus 1.000

I would be glad if I should not change manually every single "predetermined max values" per args for correct output...

ModelViewer should do...:D

TY :thumbup:

Hey LuckyBob, just a small remark on newer MVs:

Arg value slider give only minus/plus 0.999 "output" values with maximum left/right moves on the slider line while the predetermined max values are OK: minus/plus 1.00

 

You should correct it...

Well, if i change manually the "predetermined max values" to minus/plus 1.001 then the "output" will correct: minus/plus 1.000

 

I would be glad if I should not change manually every single "predetermined max values" per args for correct output...

ModelViewer should do...:D

 

TY :thumbup:

This is something new right? Im still using an older version and it goes to 100

Yes all newer version have 0.999. It caused some issue for me during animation check but I figured out what's happened. :-)

Yes all newer version have 0.999. It caused some issue for me during animation check but I figured out what's happened. :-)

I did not dig myself into it "deeply" what is this "bug" coz i prefer using older -WH1.1.1.1 official- version primarily but maybe it's only a simple, trivial problem. I just mentioned it - not a serious problem.

a question at see on the last build of edModelView, that has not only the Modelview exe, now include a great quantity of new directories. have added for new features? new directories for for moding? future improvements?

Running into a problem with old model parts here.

Trying to update an old LOM model to EDM. When I merge old animated parts (complicated MLG struts) and try to export, max crashes. If I delete those parts it will still export normally. Any suggestions as to why this might be happening?

Are the struts linked? unlink them and try

Thanks for the reply luckybob! Managed to get them to show up, it was just a duplicate material in the merged parts... had to reapply the correct ("cool") materials to each part.

New problem though (hooray,) this one has had me stumped for an hour now, figured I may as well ask. Search failed, so hopefully this will help someone in the future. I want to animate some new parts but something about the new plugins or my Max installation is giving me considerable confusion.

Previously, I was using Max 8. When I went to animate a part, I would add the animation controller (arg based rotation) and then go to town in the curve editor. It would look like this.

Now, I see this:

No X/Y/Z tracks. If I try to autokey, I get nothing. (Just rotates the part. It doesn't track back when I return the animation slider back to 0.)

mine looks the same. possibly a change in 3ds max?