SSU Development thread (4.0 to 5.0) [DEVELOPMENT HALTED DUE TIME REQUIREMENTS!]

Status
Not open for further replies.
Something is going on with the Crawler and SSU_Pad projects that makes them throw a fit against OrbiterSound, but the main vessel doesn't complain at all. I changed pretty much all project settings to match the main vessel but no luck. :facepalm:
Anyway, I did find a way to get them to work, so I'll be committing new project files for VS2017 when I sort some more of the settings out.

---------- Post added 04-24-17 at 10:44 AM ---------- Previous post was 04-23-17 at 07:06 PM ----------

I'm almost finished stadardizing the project settings and the only thing missing is what libraries should the linker ignore. For debug they pretty much all ignore msvcirt.lib and msvcrt.lib, and for release it's msvcirt.lib and msvcrtd.lib. But some also ignore libc.lib and libcmt.lib... I can't figure out if I should add these to all projects (debug, release or both) or just delete them and stick to the settings above. :idk:

---------- Post added at 12:03 PM ---------- Previous post was at 10:44 AM ----------

I'm almost finished stadardizing the project settings and the only thing missing is what libraries should the linker ignore. For debug they pretty much all ignore msvcirt.lib and msvcrt.lib, and for release it's msvcirt.lib and msvcrtd.lib. But some also ignore libc.lib and libcmt.lib... I can't figure out if I should add these to all projects (debug, release or both) or just delete them and stick to the settings above. :idk:

I added them as needed to stop the linker messages, and committed the files for 2017.
 
About the ODS/external Airlock mass discussion:

How did NASA account EVA tools and other stuff installed at the external Airlock?
 
About the ODS/external Airlock mass discussion:

How did NASA account EVA tools and other stuff installed at the external Airlock?
I believe those were charged separately. The figures I listed is the structural masses+TCS+operator equipment.
 
I believe those were charged separately. The figures I listed is the structural masses+TCS+operator equipment.

Well, it would be good to know how they these small things are accounted for being on the safe side with the masses in the NASA statistics.
 
Well, it would be good to know how they these small things are accounted for being on the safe side with the masses in the NASA statistics.
I believe those were charged as "EVA Support Equipment".
 
I think that's the most recent revision that exists online.

That's annoying.

Well, at least some solid numbers there to work with. Maybe we can one day have some interesting EVA/IVA simulation framework for SSU.
 
Why are we targeting Windows 10 now? Will we run in Windows 7? (not to mention XP...)
 
Why are we targeting Windows 10 now? Will we run in Windows 7? (not to mention XP...)

I don't want to claim anything earlier than Window 7 will work. Can somebody test it? I can only test Windows 10.
 
I don't want to claim anything earlier than Window 7 will work. Can somebody test it? I can only test Windows 10.

I'd say that targeting 7 is less trouble than targeting 10....
 
I'd say that targeting 7 is less trouble than targeting 10....
That's the only the Windows SDK version available with a clean install of VS2017 Community. I can't even't select the earlier version that comes with VC++2010 Express.
 
That's the only the Windows SDK version available with a clean install of VS2017 Community. I can't even't select the earlier version that comes with VC++2010 Express.

That's what I installed and it had version 8.1 or 10 to choose from. Could it be because I have VS2013 installed?
 
That's what I installed and it had version 8.1 or 10 to choose from. Could it be because I have VS2013 installed?
Possibly. I don't think it matters though. I could build a set of 2010-P1 SSU modules and see if it will run on Windows 7.
 
I'd say that targeting 7 is less trouble than targeting 10....

Targeting a special windows doesn't matter as long as we are not using special APIs. Anything past the standard runtime should not be a problem for us.

Maybe you didn't notice it, but you likely used the SDK for Windows 8 already for Windows 7. :lol:
 
Maybe you didn't notice it, but you likely used the SDK for Windows 8 already for Windows 7. :lol:

That's because Microsoft doesn't know how to count. :rofl:

---------- Post added at 08:09 PM ---------- Previous post was at 07:51 PM ----------

In other news, the VAFB runway is really a tough cookie to crack. I tried to put the slope, but the steps, diagonally across the runway, just don't make it much better than what it is, not to mention the problem of crossing to another tile with different data. IMO more resolution is needed to have the slope.
To make it leveled is much easier (tile crossing notwithstanding), but the source terrain has a slope... so we have to choose between 40m wall at one end, or 40m cliff at the other, or both (20m each). :facepalm:
 
That's because Microsoft doesn't know how to count. :rofl:

---------- Post added at 08:09 PM ---------- Previous post was at 07:51 PM ----------

In other news, the VAFB runway is really a tough cookie to crack. I tried to put the slope, but the steps, diagonally across the runway, just don't make it much better than what it is, not to mention the problem of crossing to another tile with different data. IMO more resolution is needed to have the slope.
To make it leveled is much easier (tile crossing notwithstanding), but the source terrain has a slope... so we have to choose between 40m wall at one end, or 40m cliff at the other, or both (20m each). :facepalm:
I still say just level the entire area. We just don't have the resolution right now and it's best just to accept that.
 
Is there animation for the External airlock hatch ?
 
Status
Not open for further replies.
Back
Top