[messire]

Hi all,

I have an issue using automxm...worked fine in 1.0, now its not working at all....
- i have named all mxm the same way as the su materials (concrete 03 in SU, and concrete 03.mxm in MR)( lets hope the space between number and name is not the issue ( got too much to rename then> suicide)
- all SU textures are using the same texture as the MR texture ( copied the folder so they use same file ( copy of it)
- its working when i am using the apply mxm material in SU, but i want it to work using automxm which is so faster!

here is a pic of the problem:



1. in SU i'm applying the materials i've preset( with same names as MR.mxm )
2. dito
3. exporting with auto mxm checked ( folder is NL/ etc..../materials/mxm files/ )
4. PROBLEM: render does not find any of the textures... strangely enough, it renders some shades, but no textures at all shall it be from SU materials, or MR mxm..


5: HELP!


> update: i have opened the file ( .mxs ) in studio, and here is how textures appear, despite the fact that i assigned the paths of textures and mxm in studio's preferences.



6: HELP

thnx!
Nils

[marked001]

i've been having the same problem :-/

[messire]

seems to be a problem with the way automxm goes looking for the textures... it produces a mxs file with no idea where the mxm are i think...
pavol?

have had the deadline issue last week too> rendered all textures directly from SU with those settings:
1. settings without huge bumps or need for reflexion or transparencies: applied sketchup material > they render as lambertian in maxwell
2. all glass i used AGS glass ( put them all on one layer in SU, then select them and use mxm material on them at once)
3. all other textures that needed bumps at all costs > assigned mxm materials one by one in SU ( as in the beta)

hope they solve the automxm issue quick> its a real time saver!
We need a tutorial with known issues ( eg do file names have other issues than not just beeing the same.. etc..)

Nils

[Richard]

Seriously guys if you are having issues with texturing, export the file, stop the render, open the file with studio and drag / drop the MXM's direct to the model save the file and then double click it to start the render.

I find it so much easier then even going through the renaming process, you can do a preview and attend anything or any shaders that need to be tweaked and the big one - add entourage without the SU bog down.

[messire]

at least that solution can solve a last minute deadline , but we are all trying to work with MR within SU, not inside the studio. KIS ( Keep it Simple) is the motto with SU, and MR plugin is a hot way to do awsome renders without having to export the file in another interface.... the idea is to set materials so they can be exported without even think about it once set in SU...
Hope they find a solution quick
Sheik must be on holiday damn him !
Where is Pavol? !


Nils

[Richard]

Don't get me wrong I agree with you regarding the ease of direct export from SU. For me though adding 3d trees and 3d textured people in SU just drags it to a holt yet I can blast around in Studio.

[Sheik]

Hi Nils,
Yes I have been on my summer vacation . How did you know? I think Pavol is also on vacation.
One thing that I notice is your SU material names do not match the names of the Arroway mxm materials.
Your SU name is concrete 9, but it should be concrete-9. It won’t be swapped unless you have exactly the same name. To avoid typos I have started using the copy-paste method (from the MXED window to the SU material). Try if that helps.
Your materials don’t appear to have been swapped, but they are default SU mats. I don’t know why they have lost the map…

I had to uninstall Maxwell and the plugin before installing 1.1 to get it working properly. Did you do that?
Sheik

[messire]

actually yes the name of the mxm jpg is not the same as the jpg in SU, but the mxm matches the Su name ( aka concrete 9 in SU is concrete 9.mxm i got rid of the -)
still does not work...
I did uninstall all MR, Plugin, and did the long backup of textures etc...

i don't like it when you say you don't know...

N.

[messire]

been a month now... do we have news on this issues...?
N

[messire]

... --- ...

[Sheik]

I asked Pavol about the automxm issue. He says he can’t reproduce the problem, but is working on it.
Too bad it isn’t working for all, as I find it is absolutely the best way of using su2mxs.
Sheik

[messire]

thnx sheick! hope pavol can save me and the others that have the issue!

N

[messire]

if that can help:


strange automxm issue again...
reinstalled the whole stuff!

can any of you tell me how you are using the SU images / maxwell images to have it work... it might all come from having two different folders, despite the same names.... how many folders do you guys use for storing textures in MR and Su???

thnx
nils

[Richard]

Certainly weird mate!

Did you check in the MXM that all maps are tiled to the same factor and have no offset?

Are the textures in the SU model painted to the base level geometry?

[Sheik]

I tried to see if I get the same problem. I used the same material as you did, and had the same name etc. I didn’t get the strange tiling problem as you did. I opened the scene in Studio, and noticed that the tiles were two different materials. The automxm one was named tiles-0.mxm (not tiles-48.mxm like the original), but was otherwise identical (a clone).
Try positioning the textures manually in SU before export. Maybe this is just caused by the mapping bug, not related to automxm.
It looks like the mapping changes at the red axis. What if you move the object?
I don’t think the folders thing is causing this. Automxm will look in subfolders of the specified folder. If there are several mxm´s with the same name in these subfolders I think su2mxs will just pick the first one it finds.
So automxm is now working after you re-installed. Did you do anything else?
Sheik