More Sovy, now with added planet!

February 2nd, 2003, 11:11 AM

Well here's a new pic. Unbelievebly this is the first time I've attempted a planet in max (I usually use Lunarcell).

Let me know what you think:

Darrell Lawrence · February 2nd, 2003, 11:45 AM

For the way the ship is lit from main lighting, you'd think the planet would be well lit too.

moovok · February 2nd, 2003, 03:16 PM

It looks fine, let me show you a diagram, done by text

o <SUN
=

The "o" is the planet and the "=" is the ship. If the sun was like this, the side wouldn't get that much sun, some, but not all. The ship itself would show a lot of light, due to the fact, we can see the front/top. That's how I see it anyway.

Melvin the Dork · February 2nd, 2003, 03:24 PM

I like it, very cool. But I agree with them, the ship needs to be darker to fit in with planet.
Mel
My two cents, worth every penny

February 2nd, 2003, 04:44 PM

For those of you interested, this mesh is now available for download in the 3D Gladiator download section.

February 2nd, 2003, 06:50 PM

Hey Trek, I downloaded your mesh and everything looks great exceot for the nacelles, the front ends of the nacelles are completely hacked up when I open the mesh in max5

February 3rd, 2003, 01:53 AM

It maybe a conversion problem (that's happened to me before converting stuff ffrom Max 2.5 to 3) caused by an error in the mesh. I'll run an STL check on them when I get home tonight and see if I can find any errors.

February 3rd, 2003, 03:37 AM

I'm having same problem in MAX4 and 5

February 3rd, 2003, 02:11 PM

Ok, ran an STL check and discovered 359 errors. Bollocks!!!!!

I'll try and fix this ASAP and get a new version up.

February 3rd, 2003, 03:37 PM

Ok, I've re-shape merged part of the bussard, the STL check raised no errors and I've replaced the zip.

February 4th, 2003, 02:58 AM

Still does the same things to me...

February 4th, 2003, 05:00 AM

Is it the Bussard or the Nacelle? (they're two different objects)

February 4th, 2003, 11:19 AM

Its the front one-fourth of the nacelle

February 4th, 2003, 01:55 PM

Found it. 5 errors caused by the boolean.

Now I just have to fix it. (Unfortunately not as easy as the Bussard).

February 4th, 2003, 04:58 PM

Ok, I've fixed the nacelle (and the STL check has given the all clear) and uploaded again.

So, who wants to try it out?

February 4th, 2003, 05:31 PM

I wouldn't mind getting a copy

, better yet I'll trade ya

.

http://www.geocities.com/kwok_wong_86 (meshes section)

February 4th, 2003, 07:13 PM

ReAder:: Go visit download section...

February 4th, 2003, 07:32 PM

I still having the same problem

Darrell Lawrence · February 4th, 2003, 07:48 PM

Alex, try an export of the nacelle to 3DS then re-import it and see if that solves the problem.

Looks like Max 4 and above may be reading something differently, causing the errors?

February 4th, 2003, 07:52 PM

Hey Alex, dumb obvoius question time ... did you collapse the mesh? Those errors usually only happen to me when I forget to collapse it.

Hito · February 4th, 2003, 07:56 PM

I have had similar issues bringing stuff from 2.5 to 3.
Collapsing all of your mod stacks before you save the file.

February 4th, 2003, 08:00 PM

And ungroup nested groups! too many can be a bad thing

February 4th, 2003, 09:24 PM

I forgot about thia till now, but will collapsing the stacks possibly fix the texture misalignment on the bottom of the saucer? I noticed the last time I downloaded it that the registry map didnt fit correctly on the bottom of the saucer

February 4th, 2003, 11:48 PM

Max 4 really doesn't like that shape merge does it.

I haven't collapsed much of the mesh (I think I might have done the saucer) mainly so that I can edit for problems like this.

Thomas - there's only one nested group in the Released version which groups the nacelles.

tgg7979 (and anyone else who's found an error)- Could you show me an image of the texture misalignmet on the saucer rings (There are seperate maps for the rings and the underside) and any other error you can find (none of this is showing on Max 3) I'll start collapsing the mesh.

February 5th, 2003, 09:57 AM

Here ya go Trek, the registry problem and the forward observation windows

seanr · February 5th, 2003, 01:36 PM

Trek, try saving it as a seperate file (rather than just saving over the original) and collapse ever single peice of that one.

February 5th, 2003, 02:00 PM

More bloody mesh errors!!! AHHHHHHH!!!!

Ok, I'm going to run an STL Check on the saucer ings and then get collapse happy on this mesh.

Sean - I plan to save the collapsd version as 9.3.1 (I don't save over the old versions as you lose models that way.

February 5th, 2003, 03:16 PM

Ok, I've taken another look at the mesh and relised that I need to spend some time giving it a good go over to get it to work in Max 4/5.

The problems seem to mainly be in the Area's of the mesh left over from Version 6. As soon as I get some serious time to spend on it I'll have a go (I need to rebuild the saucer's rings almost completely!)

February 23rd, 2003, 04:24 PM

I've updated my Sovereign Mesh to version 9.4 and is avalible in the download section.

All the stacks have been collapsed and the mesh optimised as much as possible (It now has 1/3 of the faces it did before).

Could someone with Max 4 or 5 (or both) test it out and let me know if there are any problems.