Meadville Space Center
Welcome, Guest. Please login or register.
February 29, 2020, 03:06:42 AM

Login with username, password and session length
Search:     Advanced search
Project Apollo - NASSP 6.4.3 released!
http://nassp.sf.net
25068 Posts in 2094 Topics by 2266 Members
Latest Member: twa517
* Home Help Search Login Register
  Show Posts
Pages: 1 [2] 3 4 ... 67
16  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: Apollo Training Videos on: January 29, 2010, 12:15:36 PM
Nicely done Bunyap
17  Project Apollo - NASSP / Planning / Re: Apollo 7 Initial Switch Positions on: January 15, 2010, 12:15:07 PM
Indeed.  The A7FJ will be an extremely valuable asset to what we do.
18  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: lunar landing video on: January 04, 2010, 04:41:01 AM
some of the nice things that has are things we can't because of the current Orbiter graphics limitations (hopefully to be lifted once Artlav gets OGLA to where he wants it)

Also, our CM virtual cockpit is something I don't think they had to do in EagleLander, so our resources have just be used elsewhere.... but the LM is on our TODO list and FordPerfect had started on it last I checked.
19  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: Apollo 11 mission video, Astronaut view on: January 02, 2010, 02:43:28 AM
spectacular!
20  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: Apollo 11 mission video, Astronaut view on: December 31, 2009, 10:39:50 AM
I get....

"The Video you requested is not available"
21  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 20, 2009, 03:33:54 PM
That's fine... I wasn't thinking about this as a prominent feature, more of a debug feature, and I also wasn't 100% sure I'd know where that would end up putting it at the time.  Thanks!  Thumbs Up

Gunner:
Can I see, can I see? Excited!


PS.  After the holidays calm down a bit, (Here at SpaceX we're pushing to get the first Falcon 9 to the Cape right now and I'm heading home for Christmas, so I'm busy right now) I'll sit down and we can work out the wierd behaviour of the EMS.
22  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 19, 2009, 05:40:02 AM
Hmmm well, it shouldn't be coming from my addition, which only adds to the processing requirement when you click save or it auto-saves.

Are you compiling in Debug mode? If so, switch to Release and compile that way.  Debug modules are not optimized. 

It is also possible that Tschachim does some sort of optimization of the modules when he compiles them and since you're compiling them yourself, you don't gain the benefit of those modules the you previously got with the pre-compiled modules.
23  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 15, 2009, 03:39:23 AM
The saving code is crashing on my side at random, it looks like the re-use of the EMS surface leads to an invalid device context (i.e. = 0) sometimes. I think it's better to load the bitmap directly instead:
Code:
bool EMS::WriteScrollToFile() {

//Special Thanks to computerex at orbiter-forum for assisting in this implementation
int width = EMS_SCROLL_LENGTH_PX;
int height = EMS_SCROLL_LENGTH_PY;

/////////////////////////////////////////////////////////
        // Get the drawing surface, apply the scribe line and create a corresponding
        // bitmap with the same dimensions

HDC hMemDC = CreateCompatibleDC(0);
HBITMAP hBitmap = LoadBitmap(g_Param.hDLL, MAKEINTRESOURCE (IDB_EMS_SCROLL_LEO));
HGDIOBJ hOld = SelectObject(hMemDC, hBitmap);

// Draw Commands
SetBkMode(hMemDC, TRANSPARENT);
HGDIOBJ oldObj = SelectObject(hMemDC, g_Param.pen[2]);
Polyline(hMemDC, ScribePntArray, ScribePntCnt);

SelectObject(hMemDC, oldObj);
SelectObject(hMemDC, hOld);

PBITMAPINFO bitmapInfo = CreateBitmapInfoStruct(hBitmap);
bool ret = true;
ret = CreateBMPFile("Scroll.bmp", bitmapInfo, hBitmap, hMemDC);

DeleteDC(hMemDC);
DeleteObject(hBitmap);

return ret;
}

Is this code working for you, too?

I see what you mean about the crashing, but its very odd... the code I wrote works for me, but only when there is no checklist items in the scenario.  If I get rid of those (or start from one of the base scenarios) it doesn't crash.  To be honest though, I think I would prefer to load the file like you suggest Tschachim,  I'll make the changes and recommit.  I'm not sure why it isn't overwriting your file Gunnar.... hopefully this will fix it.  Try deleting the file that is there though, just so we can check and make sure it really is writing.


EDIT: Alright, that did the trick (thanks Tschachim!), and its commited.  Gunner, try recompiling and re-running.  I changed it to write out to EMSScroll.bmp instead of just Scroll.bmp
24  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 14, 2009, 05:41:47 AM
Ahh yes... finally I discover how poorly this is implemented.  When I implemented the EMS a couple years ago, we hadn't really gotten to the point where someone could test it, and I don't have a lot of time to actually test the accuracy.  Now the fun begins!  Thumbs Up

I'm not sure why you got 0 Gs  all across...  Did you quicksave before exiting?  or Exit then restart and quicksave?

I want you to test something for me to check this real quick.  Open up your scenario, go to EMS Test 4 and let it do its thing.  Then uncover the GTA switch and flip it up.  Exit out of the simulation.   Check the bitmap and see if it printed out the test pattern.  Go ahead and tell me the results, no need to post the picture.   If you DO get the test pattern printed out, restart from the same scenario and run the reentry.  Then follow the same procedure:  uncover and flip up GTA switch then exit out of simulation.

As to the functionality of the EMS, let me refresh my memory a bit.  I don't really remember how it was supposed to work, and to be honest, it isn't all that well documented.  There's some good pdfs out there about it, I'll post them here if you're interested.  Once I get my head wrapped around the way it works again, we can start fixing the code to be more accurate.
25  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 13, 2009, 08:49:14 PM
Awesome... maybe we can get Tschachim to release modules... if not, I'll see about compiling some for you myself.

If you do try compiling your own and get stuck, just ask... but there is a very good description of what you need to do on Orbiter-Wiki to set up Microsoft's free compilers.  Good luck!
26  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 13, 2009, 03:58:37 AM
hmmm did you start from one of the scenarios you posted earlier?  If so, I'll try running it here, if not, could you post the scenario just before re-entry that you ran?

EDIT:  Are you compiling your code, or are you using the pre-compiled version?  If you are using the modules, then you'll have to wait until Tschachim releases new modules.
27  Project Apollo - NASSP / News & Announcements / Re: Virtual Cockpit Release Candidate #1 on: December 10, 2009, 12:22:39 PM
Progress has been slow... for some reason I'm having some trouble getting my head around the VC API commands... also, I just moved out to California, so I've been a bit distracted.  Right now, I'm probably going to try and get the DSKY working first...
28  Project Apollo - NASSP / Programming / Re: EMS progress/status report on: December 08, 2009, 07:34:14 PM
Updating the old topic...

I set it up so that someone can output their scroll trace... more info on the wiki page.

The way to use this feature is to make sure the GTASwitch (on the EMS) is in the up and unguarded position when either A) the simulation is saved, or B) the simulation is exited.  It is possible that the EMS needs to be powered on as well.

A bitmap file will then be created in your Orbiter root directory (where the executable is) known as Scroll.bmp.

CAUTION:  This file will be overwritten every time you hit save in Orbiter or close Orbiter with the above criteria met.

NOTE:  Since the scribe line is not saved between instances of Orbiter, if you close orbiter and reopen, then close again, the written scribe trace will only contain data created from the moment the simulation was started.

If you have any questions or problems don't hesitate to say so.
29  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 07, 2009, 03:40:09 AM
Ok, it's commited, should work just fine.

The way to use this feature is to make sure the GTASwitch (on the EMS) is in the up and unguarded position when either A) the simulation is saved, or B) the simulation is exited.  It is possible that the EMS needs to be powered on as well.

A bitmap file will then be created in your Orbiter root directory (where the executable is) known as Scroll.bmp.

CAUTION:  This file will be overwritten every time you hit save in Orbiter or close Orbiter with the above criteria met.

NOTE:  Since the scribe line is not saved between instances of Orbiter, if you close orbiter and reopen, then close again, the written scribe trace will only contain data created from the moment the simulation was started.

If you have any questions or problems don't hesitate to say so.
30  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 vAGC on: December 07, 2009, 03:16:31 AM
Great news Gunner!

After a bit of helpful debugging from some folks at orbiter-forum, I have it printing out the scroll to a bitmap file!   Thumbs Up

I'm cleaning up the code now, but once I commit it, it'll be a great tool to debug and also track manual reentries.  There will be a few catches to using it though that I'll document on the wiki once I figure them all out.

Once I commit it, I'll post here letting you know as well as telling how to use it.
Pages: 1 [2] 3 4 ... 67
Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!