I'm in a bit of a bind here. As part of the mesh updates/fixes, I have fixed the main VC mesh to fit the orbiter again. But the problem is that kills the alignment of the actual panel meshes as well as the VC positions. Could they be updated to essentially sit at local zero coordinates with the addition of offsets in the code?
SSU Development thread (4.0 to 5.0) [DEVELOPMENT HALTED DUE TIME REQUIREMENTS!]
- Thread starter DaveS
- Start date
- Status
GLS
Well-known member
Could this be delayed for a version 5.1? We could make that version just to fix the VC visuals (window issues, etc), even without the resize and panel mesh rework. This would be a small update for the user, but for us it involves many changes, hence my idea to take the VC out of the critical path for SSU 5.0.
On my end, I think I'm finally seeing light at the end of the tunnel.
A few things remain to be done, but I hope to get the aero stuff in good enough state to merge to the trunk before the end of the month.
GLS
Well-known member
There seems to have been a bit of development in the docking system department. It seems like BrianJ has come up with an actual solution in his/Donamy's SAL/HST add-on: https://www.orbiter-forum.com/showthread.php?t=40559
The active part is on the actual Service Airlock. If you want to see it in action, then just launch the Dragon2_SAL docked to HST_SCM scenario in the SAL subfolder and then press G to see the docking mechanism move with the HST.
The active part is on the actual Service Airlock. If you want to see it in action, then just launch the Dragon2_SAL docked to HST_SCM scenario in the SAL subfolder and then press G to see the docking mechanism move with the HST.
GLS
Well-known member
I'll look at this after I square away the aero stuff.
GLS
Well-known member
Fast approaching the end of the latest "chunk" of work, but I still have one major item to finish: how does the HUD know the landing gear status? The diagrams only shows the downlock indications being sent to the HUD (directly from the gear electronics), but then there are texts saying that a message is shown if the gear is up at 300ft, and another is shown when it is deploying. So, the uplock indications have to get to the HUD. Any ideas how?
Although the diagram doesn't show the uplocks anywhere, it indicates there are 10 such "direct" signals being input to the HUD, so take 3 for the downlocks, 1 for antiskid fail and 1 for NWS fail, and 5 signal inputs remain unused. It makes no sense to have some gear signals going via GPC, while others go directly, so I'm inclined to add the uplocks the same way as the downlocks. shrug:
Although the diagram doesn't show the uplocks anywhere, it indicates there are 10 such "direct" signals being input to the HUD, so take 3 for the downlocks, 1 for antiskid fail and 1 for NWS fail, and 5 signal inputs remain unused. It makes no sense to have some gear signals going via GPC, while others go directly, so I'm inclined to add the uplocks the same way as the downlocks. shrug:
Checked in the first batch of cleaned meshes/textures, this includes the following:
*ExtAL.msh
*TAA.msh
*Ku_band_DA.msh
*RMS.msh
*OBSS.msh
*OBSSMPMs.msh
*EDO_pallet.msh
*Centaur_Mission_Kit_plumbing.msh
*SLWT.msh
*ALL SRB meshes
*Orbiter.msh
I consider them frozen for release, so no more changes will be made. The rest will follow in a separate check in. Wolf: You can begin updating your hi-res textures now as the orbiter mesh is frozen.
*ExtAL.msh
*TAA.msh
*Ku_band_DA.msh
*RMS.msh
*OBSS.msh
*OBSSMPMs.msh
*EDO_pallet.msh
*Centaur_Mission_Kit_plumbing.msh
*SLWT.msh
*ALL SRB meshes
*Orbiter.msh
I consider them frozen for release, so no more changes will be made. The rest will follow in a separate check in. Wolf: You can begin updating your hi-res textures now as the orbiter mesh is frozen.
Last edited:
GLS
Well-known member
I can only take a look at this when I switch to the trunk, hopefully later this week, but a quick look at the changes in Atlantis.h shows that you reverted my changes from r2930, from way back in early December.... any reason why you are not merging the changes? :idk:
GLS
Well-known member
I said Atlantis.h, but I meant Atlantis.cpp... :facepalm:
And now Atlantis.h looks pretty messed up... just revert Atlantis.h to r2978, so it compiles again, and maybe tomorrow or Wednesday I'll switch to the trunk and re-add what's missing from Atlantis.cpp.
Checked in a working Atlantis.h to make the trunk compile again. I also checked in an updated version of Atlantis.cpp that should have the missing stuff.
---------- Post added 03-19-19 at 03:33 PM ---------- Previous post was 03-18-19 at 11:13 PM ----------
Something I forgot to mention is that currently the ODS animations are broken. I just couldn't figure out the code. Could it be simplified or otherwise better documented?
GLS's aero stuff is still being developed in the Orbitersimbeta branch, while the new mesh/textures are in the trunk. So if you want those, you'll have stay in the trunk as they only exist there. Hopefully GLS will finish his aero upgrades soon so that they can be merged with the trunk.
GLS
Well-known member
Hopefully I'll have it good enough to merge this week.
That's confirmed, I've finished all the work on it and have moved on to other things.
Don't worry, I've had my fill of that one for a while. I'll only do bug fixes on it from this point on.Gonna hold you to that !!
GLS
Well-known member
Dumped the big update in the BETA branch! SB and landing gear have correct aero now. The aerosurface positions are now saved/loaded, so there should be less of an attitude transient when starting a scenario in atmospheric flight. Recent changes to the FCS make it much less likely that a force fight between rudder and aileron will occur (with huge loss of energy due to flying a large beta angle), but it seems roll is less stable in A/L... still gets to the runway so I'll take it. :shrug:
Just switched over to the trunk and the OV looks much more tight than before! Seams now connect, so it looks smooth. :shrug:
Don't have time to look in detail today, but I found a couple of issues:
1) the PLB sides don't fully meet with the aft bulkhead
2) bottom of the RH RCC panels don't connect with the wing.
Also, a ticket should be created for implementation of the slidewire animation.
Just switched over to the trunk and the OV looks much more tight than before! Seams now connect, so it looks smooth. :shrug:
Don't have time to look in detail today, but I found a couple of issues:
1) the PLB sides don't fully meet with the aft bulkhead
2) bottom of the RH RCC panels don't connect with the wing.
Also, a ticket should be created for implementation of the slidewire animation.
- Status
Similar threads
