Idea Shuttle Fleet recompile for Orbiter 2016

[gattispilot]

Didn't see any images.

 

[Marg]

Even if you press right mouse button, and click "view image"?
Hm, all previous images I made the same way...

https://ibb.co/5TcbL6y
https://ibb.co/ggPFFBD
https://ibb.co/qnc5NZg
Links should work:
Third photo - left wing's trailing edge had the same gaps as the [now fixed] right wing.
First pic - wanted to show I noticed a while ago gaps where payload bay meets the cabins aft wall.
Second pic - red lines show that gap.

 

[gattispilot]

Yes no icon to press

---------- Post added 12-11-19 at 05:46 AM ---------- Previous post was 12-10-19 at 03:24 PM ----------

So hopefully fix the gaps. I saw some in the aft payload section. moved the camera in the cockpit back to the way it was.
CTRL+7 stows the SSME
https://drive.google.com/open?id=1xaTGEKQbw1SjTK8BlpWWiemAIdgtXavP

 

[Marg]

Seems that it is OK. Only when I look in cockpit aft camera, screen, which is to the left beside the starboard side aft window, has one poly-triangle with wrong material (half screen MFD does not show)...
https://ibb.co/3yyhQKX

 

[gattispilot]

Weird. I will fix it. Thanks for testing. I guess I can start redoing the rest of the fleet.

Do we need to look out the other aft window?


pappy2 has shown me missing some textures,meshes in the payloads.

 

[Marg]

Yes, to look out also the other aft window could be a good thing...

---------- Post added at 11:25 PM ---------- Previous post was at 09:26 PM ----------

I found some anomalies, is it EVA guy or shuttle?

https://ibb.co/4tvkJ08
It was clearly in the shadow (whole payload bay was in shadow), but seemed illuminated. Like aft wall of crew compartment is not blocking sunlight? vertical line belongs, I think, to vertical "tube like" mesh (there are two of them) on the aft wall.
But other vessels like PAM-D cradles are dark, so maybe it is EVA guy who's "to blame".

 

[gattispilot]

Fixed the aft mfd. added extra aft view

found this issue. you see the front edge of the cargo bay doors.

I have a eva guy in the bay shining his lights
https://drive.google.com/open?id=128YmGN5KxzfcIiQyct7DuFb0fH5ovXFe

not sure it is how the external mesh is displayed?

mesh_orbiter = AddMesh(hOrbiterMesh);//mesh 1
	//SetMeshVisibilityMode(mesh_orbiter, MESHVIS_EXTERNAL | MESHVIS_VC );
	SetMeshVisibilityMode(mesh_orbiter, MESHVIS_EXTERNAL | MESHVIS_VC | MESHVIS_EXTPASS);

in sf2010 it is good.

---------- Post added at 05:27 PM ---------- Previous post was at 05:53 AM ----------

I am at a lost. In the early version didn't have this issue. But I do with this meshes? Do you see the front edges of the cargo bay.

If I remove the ext pass it looks good but the eva guy isn't seen

 

[Donamy]

Try putting the EVA guy before the shuttle in the scenario.

 

[gattispilot]

But the guy is made in the scn

	mesh_orbiter = AddMesh(hOrbiterMesh);//mesh 1
	SetMeshVisibilityMode(mesh_orbiter, MESHVIS_EXTERNAL | MESHVIS_VC );

So here the cargobay door seem ok.

I add the eva guy

and go back to the shuttle

no eva guy and I noticed no payload either.

not sure if related but my meshwizard will not load up now

I think it is the camera position. If I raise it a bit you can't see the front edge of the doors.

raised it up and now you don't see the edge

but If I lower it so more center and pull back a bit:

so added the clip radius

	SetClipRadius(.1);

So not sure what is happening.

 

[Donamy]

try raising or lowering the clip radius.

 

[Marg]

Strange, I had STS-5 LAUNCH scenario, and I did not have any clipping issues, not payload doors, not that front cockpit window "thickness mesh clipping"! I switched control from ET5 to STS-5, of course, during pre-launch sequence.
Oops, payload cannot be seen in the payload bay. It is because Orbiter considers whole shuttle mesh as a cockpit, and renders in front of payloads.
I remember Shuttle Fleet had some command "RENDER" back then.
So better to have those clipping issues, but to see the payloads in the bay.

 

[gattispilot]

So I increase the clip radius and looks better.
So Marg in sts 5 close the payload doors. and see if you see the top edge of the door in the window view

 

[Marg]

Yes, in orbit - closing payload doors, they can be seen fully, even close up.
But payload is not rendered. Because whole orbiter is the cockpit...

I use D3D9 from Dec 13, 2019.

 

[gattispilot]

Can you do a screen shot of the aft window with doors shut. Not sure what you mean about the payload not rendered.

For some reason my meshwizard has died.

 

[Marg]

https://ibb.co/RCLbrVT
https://ibb.co/vsxgNV4
First pic - PAM-S cradles in STS-5 bay (outside view), but in aft cockpit view these cradles are not rendered\visible.
Also [visually] aft window frames are a bit inconsistent - part of frame is black, part - white (where window thickness is).

That's using first shuttle2016Deva.dll after correcting that aft MFD screen. And D3D9 Dec13, 2019 version for Orbiter 2016.

 

[gattispilot]

Yes I fix that the ring on the interior payload were causing it. But can you shut the payload doors and do a screen shot?

---------- Post added at 04:29 PM ---------- Previous post was at 04:17 PM ----------

Try these meshes and dll
https://drive.google.com/open?id=1Ldav0GwVkcMR0hP6_xJaA0QXl6kGQeQA

 

[Marg]

https://ibb.co/CQ4pZ36


There is some clipping, but I think, it's OK. In orbit doors are anyway mostly opened. Payload\cradles in bay are now seen, and cockpit aft windows are very much OK, also no flickering, looking at them from outside.

 

[gattispilot]

Great. But now to update the others shuttles mesh will take time. As my mesh wizard isn't working

So I will need to use another pc.

 

[Marg]

I found in MeshWizard manual:


[FONT=Arial, Helvetica, sans-serif]I get a crash to desktop with "error 68 Device unavailable" message.
Upon exiting the program, Mesh Wizard creates a CONFIG.TXT file with the settings of your last session.
This error refers to removable drive units or, if you switched computer, it may refer to unexisting drive units.
You can either delete CONFIG.TXT (and lose your custom prefs) or you may try editing it to refer to an existing path.[/FONT]

Maybe paths were changed (I mean file names, folder names) - there are references at the bottom of that CONFIG.TXT file.
If MeshWizard does not find some of those files, referenced, it may show this error.

 

[gattispilot]

So back from vacations and meshwizard working.

So It has been suggested to use the SSu textures. First can we use them? By using different directories it will not conflict with the ssu.

our present cargo bay:

same mesh but with ssu texture applied

the front and aft walls using the SSU texture would need to be re-textured.

So any ideas?

it looks like the texture for ssu maybe 4 times and large as Atlantis\

Still think the interior side below the sill should be straight down.