Originally posted by zandoria
[B]There has been a UV editor in A:M since V9(a version that will live in infamy), but there hasn’t been much documentation…Anyway here is a tutorial on using the built-in UV editor to decal a face, no flattening required!
I get a dead link with that url.
Originally posted by JTalbotski
I get a dead link with that url.
Okay I got it. Add a .htm after the uv.
It’s funny to think that in AM’s old days they had rudimentary 3d painting. Martin ditched it many, many moons ago.
Great tute William and a great plug-in Arthur!
Well, since I found out this new UV mapping stuff in AM (thanks William), I think I will focus on other projects.
Is there a need for an OBJ exporter that supports UV coords and maps from AM. If so, I hope you realize that AM decalling is more advanced then the OBJ format allows (multiple uv coords per face), and that the exporter would have to sacrifice some UV coords in place of others…
Thanks William for the UV tutorial.
You: 
A:M documentation: :annoyed:
A:M List: :shrug:
I asked some questions about texturing, maybe while you were away. This was right before the Gilles thing. No one mentioned the UV editor. I’ve been going around saying A:M doesn’t have UV coordinates! I’ve been banging my head, wishing it did, and I’m not the only one. And it actually does have it! Is everyone on the list ignorant of this? Apparently. No one mentioned it to Arthur either.
Actually, William brought it to my attention. I never knew it was there before he mentioned it - kinda shot my whole proposal, but thats fine.
I really don’t think many know that it exists…
Arthur,
What about A:M models that have more than one UV map covering the same area. This is not allowable in the .obj format, right?
So what I understand is that we can do UV coordinate mapping in AM. No need for UVMapper. And we can export an .obj and texture it. The texture files can be brought into A:M and applied to the model. No problems with having to bring the .obj model itself back in and turn it back into proper splines.
But… If we want to have an A:M model with multiple maps, then which set of UV coordinates is going to be exported? Is it possible to pick? The workaround I see is mapping the A:M model completely, with texture maps and displacement maps, for example. Then copying the model a couple of times and deleting maps on each copy so that each one has a unique set. Then export each copy as .obj and texture in DP or ZB. Then the textures should apply to the original, fully mapped A:M model.
Originally posted by jaymackey
What about A:M models that have more than one UV map covering the same area. This is not allowable in the .obj format, right?
correct
So what I understand is that we can do UV coordinate mapping in AM. No need for UVMapper. And we can export an .obj and texture it. The texture files can be brought into A:M and applied to the model. No problems with having to bring the .obj model itself back in and turn it back into proper splines.
No point in exporting a .obj file. You have the uv mapped coords, and a blank texture. Sounds like most people just put that texture into a paint program like Photoshop, and paint away…
But… If we want to have an A:M model with multiple maps, then which set of UV coordinates is going to be exported? Is it possible to pick? The workaround I see is mapping the A:M model completely, with texture maps and displacement maps, for example. Then copying the model a couple of times and deleting maps on each copy so that each one has a unique set. Then export each copy as .obj and texture in DP or ZB. Then the textures should apply to the original, fully mapped A:M model.
Yes, you can only have 1 set of UV coordinate per face. So either you pick the priority of the maps to select which uv map to use, or you do multiple .obj exports.
But, I really don’t see how this helps a whole lot. The only thing it would help with is getting the uv coords out of AM (you can already get the maps out). And this would only be useful if you were going to do something with this model in another app. Also, the texture would look a little different if the model was rendered as polygons, instead of smooth splines. So the maps may have to be corrected if the model were imported to another app that didn’t use splines.
Hope that made sense, but it sounds like you have a grasp of the problem…
I’m curious is there is another format (not .OBJ) that supports different uv maps for the different maps that can be applied to a face? .lwo? .3ds?
.ava and .ply do 
hehe
I also re-read William’s tutorial, and I noticed that he says that you can rearrange the ‘stack’ of textures. I’m wondering that if I used your .obj exporter if it would always use the ‘top’ one. This would be a little faster than making copies of models.
Most A:M people probably are using photoshop or PSP, but if they knew how easy it is to texture in ZBrush, they’d want to use it. I was texturing a peach slice today. It is so easy and actually fun to texture models in ZB. I found a free picture of a peach on a peach distributor’s website and used that for the peach skin, and then hand painted the inner flesh of the peach. It was fast. The peach slice would not be that hard to do in PS, but I just would not do more complex things in photoshop.
The distortions inherent in the photoshop workflow are not going to be any better than the distortions of working in ZB on a poly version of an A:M model. ZBrush has poly sub-division, so even a low-patch/polygon model is usually going to look pretty similar to what you would have in A:M. Think about a face like the one in William’s tutorial. Look at the UV map, and how you need to pull the chin down, open the mouth and nostrils up, etc. so that you get rid of overlap. Now you can’t just paste a picture of a face on the texture in PS, because of the distortion in the map. There are tools, I believe, for distorting a picture to fit the UV coord texture map, whether you use these, or you hand paint it, you still are doing a bit of guessing about where the laugh lines should go exactly, or where the highlights need to go, etc. The workflow is paint some in PS, then test-render in A:M to check your work, then repeat.
Thanks for listening,
In the old versions of A:M, export to a format like .3ds allowed you to bake all of your textures together and created composite maps for your exported file. I haven’t experimented with this myself, just remembering the old manual (sigh).
I’m not planning a painting tutorial, but if you are trying to figure out how to distort a photograph to match your unwrapped wire frame: Use the “liquify image” command in Photoshop 6 and up.
It creates a fine grid over the image and lets you warp it, pushing, pulling areas with a brush tool and then applying it to the original image when you are done.
Ok I would like to see if all this about AM’s UV maps really works.
Could sombody take a model say a head and apply the AM UV’s to it then export the model to say ZB or deep paint paint a map on the model then use the maps on the model in AM and have it work. Could you try it and if it works could you post what you did and how you got the texture to map to the AM model?
Thanks Dave
I have done it, but not with AM’s uv coordinates.
Works really well. Only real problems are where there are edges. DeepPaint doesn’t have splines, so it kinda smears the paint on the edges. Maybe ZBrush with subdivision would do a better job (but I don’t have ZBrush).
One of my ideas was to instead of having to reimport the whole model again in step (6), was to just read the uv coords and maps and apply that to the current model (basically keeping the splines intact). I may still do this…
Hey that sounds good about your UV idea.
Question about the AM UV thing how did you get the maps onto the AM model? does it just apply them auto like or do you have to stamp them?
Dave
The importer will import everything including uv coordinates and maps. It is all automatic with the importer.
Well, Steve has agreed to host my OBJ plugin up at the hash site. It is only for v10 and it doesn’t require the key. You can get it at:
ftp://ftp.hash.com/pub/plugins/ImportExport/windows/
and don’t think that we left you Mac folks out… (thx Ken Baer at Hash for porting it over)
ftp://ftp.hash.com/pub/plugins/ImportExport/PowerMac/
Enjoy
Originally posted by walasek
[B]
and don’t think that we left you Mac folks out… (thx Ken Baer at Hash for porting it over)
ftp://ftp.hash.com/pub/plugins/ImportExport/PowerMac/Enjoy [/B]
Thanks walasek and Ken! Now I’ve just got to upgrade.
Arthur,
Do you have a FAQ on your importer/exporter?
What all does it handle as far as geometry, textures, surface attributes?
I am interested in bringing in models that from turbosquid etc. since there isn’t a big repository of AM models for a ton of things.
The Prop importer doesn’t work too well, and I’m wondering if this might be a better way to go.
Thanks,
Originally posted by dfaris
[B]Ok I would like to see if all this about AM’s UV maps really works.
Could sombody take a model say a head and apply the AM UV’s to it then export the model to say ZB or deep paint paint a map on the model then use the maps on the model in AM and have it work. Could you try it and if it works could you post what you did and how you got the texture to map to the AM model?Thanks Dave [/B]
This actually DOES work, but you need to have an obj exporter that also creates an MTL file (Material). The workflow goes something like this:
Build and texture your model and export it as an OBJ with an MTL file.
Import this model into Deep Paint - you will most likely have to correct the paths to the maps you’ve created. If you want to do your painting in Deep Paint (i.e. create your maps), you STILL need to create maps and apply them in AM. The key is this: You are using Deep Paint to MODIFY your existing maps. The OBJ file you export for use in Deep Paint is only serving as a placeholder - you don’t give a poo about it. You modify your maps in Deep Paint, and when you are done, save them out of Deep Paint over the old maps (it’s a damn good idea to make backups of the unaltered maps).
When you open your AM model back up, it will reference your MODIFIED maps, and seams that you painted out, etc, will be fixed.
As a note, it’s a very good idea to paint all your maps into the same map - i.e. one big image that includes all your maps. This makes sure you don’t have problems with different resolutions at seams, etc. This isn’t possible all the time, but it can be very helpful.
I this technique works because it’s a technique we use here at Avalanche. The downside of Deep Paint is that things like 5-point patches and hooks play hell with it (BUT you can make a version of your model that doesn’t have any hooks or 5-pointers, then export it and use it’s mesh as placeholder just to modify the maps).
Also, I think DP is one of the worst programs I’ve ever seen in regards to interface and speed. They’ve got no competition, so they don’t feel any need to update the program. If someone came up with a better paradigm and had good OpenGL support, I’d be ALL over that…
Also, someone mentioned a problem with “stretching” when unfolding models for texturing - the easiest way to avoid this is to keep the distances between the CPs as close as possible to what they are when the model is in it’s natural state. This can be tough, but it’s critical to keeping the maps clear. I find that the easiest way to do this is to use the rotate tool to move points into the same plane - it’s cumbersome, but I don’t get as much stretching…
JoeW