topic transfering uvw data via maxscript in 3ds Max Programming Forum

transfering uvw data via maxscript

Anonymous — Thu, 11 Feb 2010 18:25:33 GMT

i am completely new to maxscript, so maybe this is a dumb question:
i am trying to use maxscript to transfer uvw coordinates from one object to another.
my test file contains a poli called 01 and another one called 01a (the final file will have a series of such groups (02/02a, 03/03a,...)).
01 has an unwrapUVW modifier containing the correct cordinates which should be transferred to 01a.
i tried with recording a drag and drop action of the modifier, but this did not work.
i also tried to safe and load the uvs with the following script:


macroScript Macro27
 category:"DragAndDrop"
 toolTip:""
&#40;
 actionMan.executeAction 0 "40021"  -- Selection: Select All
 macros.run "Modifier Stack" "Convert_to_Poly"
 &#36;.material = meditMaterials
 clearSelection&#40;&#41;
 select &#36;a1
 subobjectLevel = 4
 &#36;.EditablePoly.attach &#36;1 &#36;
 subobjectLevel = 0
 modPanel.addModToSelection &#40;Uvwmap &#40;&#41;&#41; ui:on
 &#36;.modifiers.length = 40.71
 &#36;.modifiers.width = 210.34
 modPanel.setCurrentObject &#36;.baseObject
 subobjectLevel = 4
 &#36;.EditablePoly.SetSelection #Face #{1}
 actionMan.executeAction 0 "40020"  -- Edit: Delete Objects
 &#36;.EditablePoly.delete #Face
 subobjectLevel = 0
 modPanel.setCurrentObject &#36;.modifiers
 modPanel.addModToSelection &#40;Unwrap_UVW &#40;&#41;&#41; ui:on
 &#36;.modifiers.unwrap.save &#40;&#41;
 select &#36;t1
 modPanel.addModToSelection &#40;Unwrap_UVW &#40;&#41;&#41; ui:on
 &#36;.modifiers.unwrap.load &#40;&#41;
&#41;

basically it works, but it asks me where to safe the uvw-file and then again asks which uvw file to load, which is not so convinient. can i specify a path in the script, which says where to save and load the uv date?
of course i would prefer transferring the data without saving in between.
any help would be appreciated

Re: transfering uvw data via maxscript

Anonymous — Thu, 11 Feb 2010 19:34:15 GMT

Maybe is a too simple idea, but why not to try just to copy modifier?

-- just example
-- myPairs = #&#40;&#36;objA, &#36;objB&#41;
addModifier &#36;objB &#40;copy &#36;objA.modifiers&#41;

Re: transfering uvw data via maxscript

Anonymous — Fri, 12 Feb 2010 09:26:19 GMT

thanks for the quick response!
basically it works, the modifier is transferred.
the problem is: the uvw-coordinates are not transferred.
when doing the same with a simple bend modifier or uvw mapping, it works as expected, all the settings within the modifiers are transferred.
btw: both my objects are prepared for uvw matching (same vertex count, etc.). tranferring manually via .uvw-file works fine

Re: transfering uvw data via maxscript

Anonymous — Fri, 12 Feb 2010 13:24:09 GMT

Yes, I know, load/save via MaxScript without popup dialog feature is asked many times, unfortunately is not implemented yet.

Re: transfering uvw data via maxscript

Anonymous — Fri, 12 Feb 2010 16:06:20 GMT

i see ....
do you know, if it is possible to specify a certain file name and path to temporarily safe and load the uv file?

Re: transfering uvw data via maxscript

Anonymous — Fri, 12 Feb 2010 21:10:59 GMT

nope 😕 so em i wish to do this... nor yet third party SDK extensions for this.

Re: transfering uvw data via maxscript

Steve_Curley — Fri, 12 Feb 2010 22:41:56 GMT

It is possible, but messy.

I cannot guarantee this will work on all systems - I don't have Vista or Win7 to try it on.
It does appear to work on XP-64.

Use at your own risk!

Also, if you get the situation where you would be overwriting a file, you will get the "Overwrite Yes/No" dialog. It would be best to ensure that the file does not exist (using the normal getFiles and deleteFile functions), though the following code could be expanded (duplicated, almost) to spot that dialog and auto-press the Yes button.

Enjoy - I'm off to sunnier climes where you (hopefully) can't find me...


DialogMonitorOPS.unRegisterNotification id:#eyeInTheSky

fn dmnotification = 
&#40;
WindowHandle = DialogMonitorOPS.GetWindowHandle&#40;&#41;
WindowName = UIAccessor.GetWindowText WindowHandle
if WindowName != undefined then
   &#40;
   if &#40;findString WindowName "Save UVW"&#41; != undefined then
      &#40;
      cWindows = UIAccessor.GetChildWindows WindowHandle
      entryField = 0
      for t = 1 to cWindows.count do
         &#40;
         if cWindows != 0 then
            &#40;
            if &#40;UIAccessor.GetWindowClassName cWindows&#41; == "ComboBoxEx32" then
               entryField = cWindows
            &#41;
         &#41;
      if entryField != 0 then
         &#40;
         UIAccessor.SetWindowText entryField "C:\\Temp\\tmp.uvw"
         UIAccessor.PressButtonByName WindowHandle "&Save"
         &#41;
      &#41;
   &#41;
true
&#41;

DialogMonitorOPS.RegisterNotification dmnotification id:#eyeInTheSky
DialogMonitorOPS.Enabled = true

&#36;.modifiers.unwrap.save&#40;&#41;

DialogMonitorOPS.Enabled = false
DialogMonitorOPS.unRegisterNotification id:#eyeInTheSky

NB. This is one occasion where you cannot use "C:/Temp/Filename.ext" - you must use the \\ version.

Re: transfering uvw data via maxscript

Anonymous — Fri, 12 Feb 2010 23:10:32 GMT

Wow, Steve, you're awesome person! Thanks a lot! :))

Re: transfering uvw data via maxscript

Steve_Curley — Fri, 12 Feb 2010 23:21:48 GMT

It's not really much more than a modification to the sample code in the help for the UIAccessor functions. They tricky bit is having to run it (with lots of debug prints) to find the actual window you want, bearing in mind that every button, toolbar even the static text is a "window". Once you know which one you want it's not too bad.
Still a messy way to have to do it when a built-in function (with options for the filename, overwrite and so on) really shouldn't be too difficult to implement.

Re: transfering uvw data via maxscript

Anonymous — Sat, 13 Feb 2010 00:12:12 GMT

I must admit that I had not the courage to play with the UIAccessor (yet) :)
Sincere thanks for all your help and tips!

Re: transfering uvw data via maxscript

Steve_Curley — Sat, 13 Feb 2010 10:21:54 GMT

You're welcome :)

If you want a different example of using the UIAccessor functions see this thread. Fun and games trying to toggle a checkbox :)
I had to google for how to do that one...

Re: transfering uvw data via maxscript

Anonymous — Sat, 13 Feb 2010 13:34:27 GMT

A very useful example, thanks! It pointer me to the next step. You wrote a "clean" function (without arguments) and pass variable by changing globals, I like this trick :) Thanks again!

Re: transfering uvw data via maxscript

Steve_Curley — Sat, 13 Feb 2010 13:53:45 GMT

You don't actually have much choice in that instance. Remember that the function is being called by a Windows Event - rather like an "on button pressed" routine in a dialog, but without knowing which button was pressed. The script reacts to the opening of the dialog so you can't really pass parameters to it because you (the rest of the script) didn't call it directly. A Global seemed the easiest way of getting around that :)

Re: transfering uvw data via maxscript

Anonymous — Sat, 13 Feb 2010 17:43:10 GMT

hi steve,
thanks for the help.
i will try to build it into my script. as i said, i am an absolute beginner, so it will take some time to check it.
i am on x64, so hopefully it works.

Re: transfering uvw data via maxscript

Steve_Curley — Sat, 13 Feb 2010 20:14:03 GMT

You're welcome. Just bear in mind that the above script only deals with the saving of the UVW file - you would need to deal with the loading of it by duplicating part of the function, checking for the different dialog and possibly a different component too.

Re: transfering uvw data via maxscript

Anonymous — Sun, 14 Feb 2010 21:56:53 GMT

I'm still on "save" handle 'cause the issue is complicated :) but I think to share what I let out and how I solve (or plan to solve) incoming trammel, just to can help to others who plan to fight with this :)

So, first, buttonOPS are binded to their rollout, or shortly - Modify panel must be open and Unwrap_UVW modifier must be selected; else the "lovely" error ("system exception") will appear.

b = box&#40;&#41; -- create Box
m = Unwrap_UVW&#40;&#41;
addModifier b m
max modify mode -- open modify panel
modPanel.setCurrentObject m -- select Unwrap_UVW modifier
-- then call ...
m.save&#40;&#41;

The second is bound to Max2009. In Max9 test shown no problem. So... to test in Max2009 just continue above example by executing (line by line) this code:

m.save&#40;&#41; -- "sleep"
m.load&#40;&#41; -- "sleep"
m.save&#40;&#41; -- now works
m.load&#40;&#41; -- now works

Shortly, some "sleep" bug in Max2009 tied to Unwrap Save/Load functions. They return OK but not execute corresponding dialog window, and "wake up" only...:
after push the button manual (at least once).
after call them in cross order, (inconvenient way) i.e:

m.save&#40;&#41; ; m.load&#40;&#41; ; m.save&#40;&#41; -- to save .uvw
m.load&#40;&#41; ; m.save&#40;&#41; ; m.load&#40;&#41; -- to load .uvw

If repeat the test, you'll see the functions need "wake up" for each modifier. This complicate the task too much 😕 If going in this direction then 'cause there no way to detect MaxScript accessibility to the functions, you'll need to reset Max, reopen the file and call both function for each modifiers. Not only complicated but not (always) works smoothly as well.
Well... I found third way too:
after "edit()" both (save/load) function react as needed/expected. So, now I'll need (i.e. I plan) to write DialogMonitorOPS for "edit" too to can fix this in Max2009.

Here is my auto-close callback for edit uvw dialog:

DialogMonitorOPS.unRegisterNotification id:#wakeupUnwrapButtons

fn closeEditUvwDialog = 
&#40;
    WindowHandle = DialogMonitorOPS.GetWindowHandle&#40;&#41;
    WindowName = UIAccessor.GetWindowText WindowHandle
    if WindowName != undefined do
    &#40;
        if &#40;findString WindowName "Edit UVWs"&#41; != undefined do
        &#40;
            UIAccessor.CloseDialog WindowHandle
            subobjectLevel = 0
        &#41;
    &#41;
    true
&#41;
DialogMonitorOPS.RegisterNotification closeEditUvwDialog id:#wakeupUnwrapButtons
DialogMonitorOPS.Enabled = true

&#36;.modifiers.edit&#40;&#41; -- test

DialogMonitorOPS.Enabled = false
DialogMonitorOPS.unRegisterNotification id:#wakeupUnwrapButtons

Any better solution (if you know?) is welcome of course.

Re: transfering uvw data via maxscript

PiXeL_MoNKeY — Tue, 16 Feb 2010 23:41:14 GMT

If the vertex count is the same then you may want to look at ChannelInfo or using the Projection modifier to transfer the mapping data.

-Eric

Re: transfering uvw data via maxscript

Anonymous — Wed, 17 Feb 2010 02:42:06 GMT

Thanks for your advice, ChannelInfo or Projection help in any cases... However, manual copy/paste unwrap_UVW also works fine, just doing via MaxScript is wrong but... I have a good news... I found a very elegant solution using "swap" function (an awesome miscellaneous funcion that save my *** :) many times in a lot of situations). If anybody need my way, I'll share "how to". Thanks again for the reply.

Re: transfering uvw data via maxscript

Anonymous — Wed, 17 Feb 2010 07:20:33 GMT

You’re welcome. Just bear in mind that the above script only deals with the saving of the UVW file - you would need to deal with the loading of it by duplicating part of the function, checking for the different dialog and possibly a different component too.

thanks again for the elaborate explanation.
sounds good so far.
think i will take some help to adhere your tips.
cheers roberto

Re: transfering uvw data via maxscript

Anonymous — Wed, 17 Feb 2010 07:22:04 GMT

If the vertex count is the same then you may want to look at ChannelInfo or using the Projection modifier to transfer the mapping data.

-Eric

sounds promising.
i will give it a try and feedback