SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
I don't have the .msh import/export script for GMAX.
 
I don't have the .msh import/export script for GMAX.
Here you go: [ame="http://www.orbithangar.com/searchid.php?ID=4185"]max2msh v1.3[/ame]
 
There's been a lot of discusson recently about who is responsible for this situation, and I don't think it's useful. We all saw the changes DaveS was making to the mesh when he checked them in. It would have been nice if someone pointed out the issues with the mesh at the time, instead of months later, but that doesn't help us now.

GLS's suggestion of going back to the 2.1 branch mesh is a good idea, but I suspect that after resizing the mesh, we'll wind up redoing a lot of the animations anyway. DaveS, can you do a quick resize and see what happens to the animations?

In case resizing doesn't work, I'm working on undoing the changes in Rev. 1601. I'll check the result into a branch, and we can go from there.
 
Animations no longer good I'm afraid.

And how does it look? If it doesn't have problems, I think it's still better to clean it up and redo the animations (it's just (lots of) numbers in the code right?), than going back to 2013 and probably still have to redo lots of things.
 
And how does it look? If it doesn't have problems, I think it's still better to clean it up and redo the animations (it's just (lots of) numbers in the code right?), than going back to 2013 and probably still have to redo lots of things.
Not good. Everything is off.
 
I've created a new branch (Mesh-Rev1463), which contains the latest revision (rev. 1814) after undoing the changes in Rev. 1601. I've only done minimal (very minimal) testing, but the results are surprisingly good.

Can someone take a look and see if the mesh in this branch needs any changes?
 
I've created a new branch (Mesh-Rev1463), which contains the latest revision (rev. 1814) after undoing the changes in Rev. 1601. I've only done minimal (very minimal) testing, but the results are surprisingly good.

Can someone take a look and see if the mesh in this branch needs any changes?
The mesh has the previously reported star tracker errors.
 
It doesn't really matter what happened, what matters is we get a working mesh without the probelms released. The resizing was fairly recent as far as I know. Can't we go back to a revision before the resizing?
 
It doesn't really matter what happened, what matters is we get a working mesh without the probelms released. The resizing was fairly recent as far as I know. Can't we go back to a revision before the resizing?

I would rather tolerate small errors than a big error by having completely wrong dimensions. For myself, I can't separate dimensional quality from visual appeal, either it does both equally well for a simulation, or it does both as bad as the lowest quality of the two.

And WTF is the problem with the Star Trackers that it can't get fixed?
 
And WTF is the problem with the Star Trackers that it can't get fixed?

I second that.
Isn't it possible to copy that section from the "good 2013" mesh and past it onto the current one?
 
To me it looks good.

---------- Post added at 08:40 PM ---------- Previous post was at 08:00 PM ----------

I second that.
Isn't it possible to copy that section from the "good 2013" mesh and past it onto the current one?
I proposed this earlier:

I am willing to make a compromise: The FWD fuselage from 1462 which is good and everything else from the current WIP. That will get us all the fixes.
 
Model looks fine !!
 
To settle the size question once and for all: If you are in favor of dimensionally accurate meshes, please add your thanks to this post.
 
I thought it was determined, your scale was wrong ?
 
I thought it was determined, your scale was wrong ?

I have spent the last few weeks correcting that. You are free to verify this: 210x0.0254=5.334
 
Can we get a release on OH ? It would sure eliminate alot of confusion.
 
Status
Not open for further replies.
Back
Top