Simple request to all users of a newest version:
Is anyone experiencing problems with tight test during the export phase?
Please, let me know if you do.
In the M3 - Export tool you have new options: Add Bones and Scene test
Now these two buttons are there to help you out.
Scene test tests if the scene is ready to be exported. The exported DOES NOT add any bones during the export. So if you don't add bones, they won't be there.
Add bones adds bones to the selected nodes/geometries at their pivot points and binds them together.
Hey, Leruster! Check the screen. Using max2010, created 3 bones and a ribbon. Checked scene. It found no errors. Pressed Export. Got what you see on the screenshot.
Then added a mesh. Applied material. Checked scene. It said that mesh has no sc2 material. But it had.
UPD: Tried a simple thing: added a mesh, created a bone by the button, exported, got the error again.
UDP 2: Kailniris said he's using 2010 too, so looks like it's the reason why we have the error.
I new test 2.2 version xelnaga tower max10 version.
Ribbon does not work and there is a shift in the bones, or the geometry.
Please someone check max11!
Funny thing. I'm using 2011 and I don't have to have tight test to export, the script just adds default tight during export :/ (kind of null tight test).
@Kailniris2: Go
If you do any test with it, I'm very curious to see if it works for you or not. If you could share, that would be great :)
I first test 2.2 version battlecruiser_dead model. I could not export the old error (attachment). I really like the layering system.
Simple request to all users of a newest version:
Is anyone experiencing problems with tight test during the export phase?
Please, let me know if you do.
@Kailniris2: Go
Does the attachment have a bone?
I just started from scratch one cube and one bone. Now, "Init" I got an error message. I have attached the error message
@Kailniris2: Go
Did you run the sc2objects.ms?I don't even :/@Kailniris2: Go
create a bone and create a tight test, link everything to the bone. should work.
Should have mention that:
In the M3 - Export tool you have new options: Add Bones and Scene test Now these two buttons are there to help you out.
Scene test tests if the scene is ready to be exported. The exported DOES NOT add any bones during the export. So if you don't add bones, they won't be there.
Add bones adds bones to the selected nodes/geometries at their pivot points and binds them together.
I recommend using that quite often :)
please send me a working version of 3ds max object.
@Kailniris2: Go
You have it in your .zip file :)
@Leruster: Go
fell behind the file
@Kailniris2: Go
What? :)
the file in the zip is not working for me and i don't know why
@Leruster: Go
Hey, Leruster! Check the screen. Using max2010, created 3 bones and a ribbon. Checked scene. It found no errors. Pressed Export. Got what you see on the screenshot.
Then added a mesh. Applied material. Checked scene. It said that mesh has no sc2 material. But it had.
UPD: Tried a simple thing: added a mesh, created a bone by the button, exported, got the error again.
UDP 2: Kailniris said he's using 2010 too, so looks like it's the reason why we have the error.
@Zolden: Go
add a tight test, attach it to a bone. the error is because it's not finding a tight test. they are mandatory to export right now.
@maverck: Go
Yeah, worked, thank you!
I new test 2.2 version xelnaga tower max10 version. Ribbon does not work and there is a shift in the bones, or the geometry. Please someone check max11!
@Kailniris2: Go
The lightnings are not just ribbons, they use sRib structure which is not implemented.
@Zolden: Go
Funny thing. I'm using 2011 and I don't have to have tight test to export, the script just adds default tight during export :/ (kind of null tight test).
@Leruster: Go
The "Ribbon" smaller the problem, the bigger the geometry error.
Everything works now. Managed to create a ribbon.
Btw, how can we map a texture to a ribbon? It odesn't show unwarp UVW modifier in the list for ribbon object.
@Leruster: Go
Ok, ribbon test (detonate.m3 model) The imported values are not good, after a slight modification: