ADSWNJ
Scientist
- Joined
- Aug 5, 2011
- Messages
- 1,667
- Reaction score
- 7
- Points
- 38
I've been keen to get into coding MFD's for orbiter. I picked Glideslope as it's one of my favorite MFD's and just awesome for doing dead-stick landings on the XR-series ships (my all-time favorite vessels).
I have been working on the original Glideslope source code distributed with the current Glideslope package, which appears to be the original Chris Jeppesen code, rather then the updated and compiled version KWAN3217 released.
I have tried to get in touch with KWAN3217 to no avail - so Kwan if you are there, I'd love to compare notes with you offline.
I have been able to stub in code to fix up the missing compile links (EngUnit code) to make the original version compile, and I have been fixing up loads of minor things that irritated me with the current version (e.g. font size and scaling, tape sizing, AOA and Glideslope number positioning). I have also added a digital reentry parameters display if like me you prefer flying on a set of numbers rather than working from the tapes display. I have also been tuning the reference glideslope for the XR ships as opposed to the original shuttle.
Things I need help with ...
(1) I need some code to do the menu select of the landing location and runway, versus the Prev base / Next Base. Does anyone have anything I can reuse?
(2) I want to persist the selections (e.g. modes) for the various MFD's ... e.g. if you are running left MFD, right MFD and an Ext MFD, with the glideslope on one, digital reentry on 2 and horizontal view (HAC) on Ext, then I want this to come back again when restarting the current settings save.
(3) On resizing the ExtMFD, it's resetting the mode. Probably just my ignorance for what is being reset where, but I don't have any good documentation of what callbacks get called on various events, so it's a bitch to debug by hand.
Before I release a package or any code - I want to be respectful of the previous author's work, and I want to give fulsome credits where appropriate. (Hell - after staring at this code for several days, I am still in total awe at the intricacy of the flight calculations I presume Chris Jeppesen originally wrote, and I am really still scratching the surface with my understanding of exactly how the vectors and matrices are being manipulated.) Too bad the code is severely tersely documented, but it makes for a hell of a detective job.
Anyway ... let me know what you think, and the protocol for releasing an update to prior art where I cannot contact the authors.
I have been working on the original Glideslope source code distributed with the current Glideslope package, which appears to be the original Chris Jeppesen code, rather then the updated and compiled version KWAN3217 released.
I have tried to get in touch with KWAN3217 to no avail - so Kwan if you are there, I'd love to compare notes with you offline.
I have been able to stub in code to fix up the missing compile links (EngUnit code) to make the original version compile, and I have been fixing up loads of minor things that irritated me with the current version (e.g. font size and scaling, tape sizing, AOA and Glideslope number positioning). I have also added a digital reentry parameters display if like me you prefer flying on a set of numbers rather than working from the tapes display. I have also been tuning the reference glideslope for the XR ships as opposed to the original shuttle.
Things I need help with ...
(1) I need some code to do the menu select of the landing location and runway, versus the Prev base / Next Base. Does anyone have anything I can reuse?
(2) I want to persist the selections (e.g. modes) for the various MFD's ... e.g. if you are running left MFD, right MFD and an Ext MFD, with the glideslope on one, digital reentry on 2 and horizontal view (HAC) on Ext, then I want this to come back again when restarting the current settings save.
(3) On resizing the ExtMFD, it's resetting the mode. Probably just my ignorance for what is being reset where, but I don't have any good documentation of what callbacks get called on various events, so it's a bitch to debug by hand.
Before I release a package or any code - I want to be respectful of the previous author's work, and I want to give fulsome credits where appropriate. (Hell - after staring at this code for several days, I am still in total awe at the intricacy of the flight calculations I presume Chris Jeppesen originally wrote, and I am really still scratching the surface with my understanding of exactly how the vectors and matrices are being manipulated.) Too bad the code is severely tersely documented, but it makes for a hell of a detective job.
Anyway ... let me know what you think, and the protocol for releasing an update to prior art where I cannot contact the authors.
