Could Windows XP SP3 be the cause of my problems?  I’m really bummed out about this- been totally hyped about getting mudbox for a long time (takes forever to get the military to approve things) and now that I have have it I can’t even use it.  If Autodesk doesn’t get this app debugged with a new sp or a comp full point upgrade I’m going to have a hard time writing a justification for future upgrades.

Any help would be much appreciate- Thanks,

TK

-TK

...Just noticed that the Foam brush is acting like the smear brush too…

WTF!?! Is anyone else having any problems like this?

-TK

Mudbox normal maps won’t work in Max…

Hi All,

We’re developing a rather organic looking model in Mudbox (2009) and seams are showing up from the generated normal maps when viewed in Max (2009), and in other applications as well.

We’ve just done a simple test with a torus, and it appears that even with this model and the default settings in Mudbox we still can’t get Mudbox’s generated normal maps to display in Max without seams showing.

The model doesn’t use any mirrored or overlapping UV’s, although we did bend the torus, then relax the UV’s in order to get some more “organic” UV mapping like on our actual model.

Steps to replicate this are as follows:
1) Make a simple Torus in Max and move the UV’s around a bit so the edges don’t line up perfectly parallel in UV-space.. (we did this by bending the torus and then relaxing the UV’s).
2) Sculpt it a bit in Mudbox and generate normal maps for it.
3) View it in Max using the Mudbox-generated normal map.. Turn up the specular and/or increase the normal map intensity to make the seams more obvious.

Our actual model is nicely mapped, but we have seams showing everywhere a whole lot worse than this. It’s not possible to hide the seams any more than they currently are. Apart from seams resulting from very low-resolution normal maps, one would expect that Mudbox should be able to correctly generate normal maps to have completely invisible seams when rendered?!?!?

	Attachment

	Attachment

	Attachment

	Attachment

Hello All,

I am having the devil of a time exporting a displacement map out of Mudbox.

Image one is what I see in Mudbox. I step down to the level 0 and select it as the target mesh (low res) and press Use Selected. I uncheck Smooth Target Model and Smooth Target UVs.

I step up to level 4 which has about 8 million polygons and image 2 is what I see. I select it and add it as the Source mesh using Add Selected. Using the settings shown, I hit extract. Bingety Bangety Bongety. I have tried with Best Guess clicked. Map extracts with no errors.

Image 3 is what shows up in Photoshop. I’m no expert, but it looks like it hasn’t smoothed anything.

Image 4 is what renders in Maya 2009. Yes, I have the approximation editor set properly-The console tells me I have twice the number of triangles as I do.

I am using the trial OS X version of Mudbox 2009 and rendering with Maya 2009 on a 24 inch iMac 3.06 ghz Intel Core 2 Duo proc, 4Gb or RAM and OS X 10.5.8.

I suspect it is something in the map extraction. Does anyone have any ideas? I would like nothing better than to be made a fool of by someone saying flip that switch there, or click that button. Thanks in advance!

Excelsior!
ekunzendorf

	Attachment

try to displace the lowress with your dispmap in mudbox…

subD the lowres to the same level like your high…
go to maps --> sculpt maps using dispmap…
if your model looks ok, its not the map its your render…

Problem Solved, sort of.

The good news is that the problem is not the map per se. The image on the left in mudbox is the result of modeling with the displacement map. Not exactly the same as what I originally had, but closer than Maya’s render.

After a lot of button pressing and switch flipping in Maya, I found the answer and got the image at right in Maya. TURN OFF TEXTURE FILTERING!!! It is front and center in the File texture attribute editor. Click, done. :S I don’t recall seeing that in any of the tutorials I read or watched. Also, (and I don’t know if this is part of the answer or not) loading the OpenEXR loader in the plug-ins loader also was something I did as part of trying to work through the solution. It at least allowed the file texture to have a preview in the material attribute editor! :)

I also believe (and feel free to disagree or confirm) that I had Smooth Positions unchecked in the Add New Subdivision Levels options. I suspect that that may be causing the unpleasant pixelation in the displacement map. I will probably resculpt with that option enabled and see what happens. Thank you Oglu for being patient.

Excelsior!
ekunzendorf

	Attachment

When trying to export this .mud to a fbx file in Mudbox2010, MB stops working and delivers

Problem signature:
Problem Event Name: APPCRASH
Application Name: mudbox.exe
Application Version: 4.0.0.0
Application Timestamp: 4a708500
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791adec
Exception Code: c0000374
Exception Offset: 00000000000a6e97
OS Version: 6.0.6001.2.1.0.256.6
Locale ID: 1053

I’ve had some problems with importing and crashing files with turned edges (and it might be that still). But this file is orginally the default mesh from mudbox, exported to fbx for some remodelling in max, only to be exported back to mudbox for retouching.
(just for a quick work / test). 

However, now that ive spent an hour or two on it, with multiple subdivides, i cant export it back to max. I’ve attached this mud here (only the lowest level), so you can see if you can figure out what im doing wrong.

I’ve tried another model with same steps, and it works just fine.

OPERATING SYSTEM
Name: Microsoft® Windows Vista™ Business
Version: 6.0.6001
Service Pack: 1.0
Architecture: 64-bit
Registered User: smek
Language: 1033
Domain Role: 0
Total Physical Memory: 4093 MB
Total Virtual Memory: 8388607 MB

PROCESSOR
Number of Processors: 1
Logical Processors: 2
Manufacturer: GenuineIntel
Name: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz
Version: Model 15, Stepping 11
Description: Intel64 Family 6 Model 15 Stepping 11
Address Width: 64
Number of Cores: 2
Max Core Speed: 3060 MHz

VIDEO
Card Name: VNC Mirror Driver
Memory: 133 MB
Driver Name: 1.8.0.0
Driver Version: 1.8.0.0
Video Mode: 1.8.0.0

File didnt upload last time. (or this time?)
http://www.davidsoderstrom.se/div/brute_low.zip

I installed the Entertainment Suite on a Mac Pro with Vista 64 running through bootcamp.  It’s been working fine (Maya, Max, Motion Builder, Mudbox, etc...). 

Yesterday after quitting Mudbox the apps just quit working.  It gives an error message like “The application Mudbox has quit working.  Windows is searching for a solution.  Closing...”

I uninstalled Mudbox and reinstalled it, but there was no change.  I also deleted the Mudbox directory in My Documents.  It doesn’t say it can’t find a license.  I’m typing in the serial number and key from the installation box.  The apps don’t install until you’ve typed in a valid number and key, anyway.

This occurs on start-up of the applications and running as Administrator doesn’t help.  I also downloaded and installed the latest video drivers for my nVidia Geforce 285.

Any ideas what is up here? What would cause all of them to fail but not give a licensing message?

Hey guys, i’m having a problem with mudbox right now. I just went from xp 32bit to w7 64bit and ever since mudbox has stopped working prectically at all because whenever i import a mesh into it and subdivide it to a specific number of times (that number differs) i get ultra low fps in the viewport (1-2).
Now i don’t know what to say about this cuz on xp it ran flawlessly i hope you guys have any solution.

My specifications are:
windows 7 ultimate 64bit
intel core 2 quad 2.4 ghz
nvidia 9600gso 768 mb
2 gb ram
mudbox 2009 32bit