Space Shuttle Ultra development thread

I got it to compile with the .cpp and .h files in separate folders using the professional version of VS 2005. I can update the project files on sourceforge if you want to go back to the old arrangement.
 
I got it to compile with the .cpp and .h files in separate folders using the professional version of VS 2005. I can update the project files on sourceforge if you want to go back to the old arrangement.
How about checking in the updated VC++2005 sln file? It might be that I have a setting or two wrong. So let's try that before movig any file again.
 
How about checking in the updated VC++2005 sln file? It might be that I have a setting or two wrong. So let's try that before movig any file again.

Well, try that, maybe it helps. But I think that moving the source files (cpp) into the root folder, might also only be a minor pain. The header files are more important for the structure, as they can control the visibility of information.
 
I just managed to build SSU using VC2008Pro, so it is at least possible in both Pro versions. I can commit some updated project settings for VC2008, needed to ignore one library more, maybe VC2005 users will get problems with the settings.
 
I just managed to build SSU using VC2008Pro, so it is at least possible in both Pro versions. I can commit some updated project settings for VC2008, needed to ignore one library more, maybe VC2005 users will get problems with the settings.
Well, check it in and we'll see.
 
...fingers crossed !;)
 
Well, seems like I need to upgrade as VC++2005 complains that the files are too new for it to open.

VC2008 Express has no problems with the 2008 files, but I think that VC2005Pro might get the same problems then. I could recreate all project files in a VC2008 folder, so we don't get conflicts with 2005 again. But it would mean each language version has to be maintained by somebody. I can now offer to maintain 2008, I will stop working with VC6 soon.
 
VC2008 Express has no problems with the 2008 files, but I think that VC2005Pro might get the same problems then. I could recreate all project files in a VC2008 folder, so we don't get conflicts with 2005 again. But it would mean each language version has to be maintained by somebody. I can now offer to maintain 2008, I will stop working with VC6 soon.
I think that would be a good idea. I'm currently installing VC++2008 Express Edition, so I should be able to check out the current files.
 
OK, VC++2008 installed, now I'm going to see if it compiles.
 
No luck. It complains that it cannot find msvcirt.lib, despite I have told the linker to ignore it along with msvcprt.lib.
 
Any updates on this? It will be kinda hard for me to verify a proper fit of the FSS/RSS with an SSU vehicle and I'm kinda short on those after the last few days of failed builds.
 
Can't help you on this, I have successfully ignored msvicrt.lib in my settings as it collides with the default orbiter libs. Does somebody have an update on the opaque HUDs already?
 
Well, here's the build log:

Code:
[SIZE=1]
1>------ Build started: Project: Atlantis, Configuration: Release Win32 ------
1>Linking...
1>MSVCRT.lib(ti_inst.obj) : error LNK2005: "private: __thiscall type_info::type_info(class type_info const &)" (??0type_info@@AAE@ABV0@@Z) already defined in LIBCMT.lib(typinfo.obj)
1>MSVCRT.lib(ti_inst.obj) : error LNK2005: "private: class type_info & __thiscall type_info::operator=(class type_info const &)" (??4type_info@@AAEAAV0@ABV0@@Z) already defined in LIBCMT.lib(typinfo.obj)
1>LINK : fatal error LNK1104: cannot open file 'msvcirt.lib'
1>Build log was saved at "file://c:\OrbiterUltra\Orbitersdk\Space Shuttle Ultra\Release\BuildLog.htm"
1>Atlantis - 3 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
[/SIZE]
 
If I had a correctly scaled, working VC, I could fix the opaque HUDs in 2 sec.;)
 
If I had a correctly scaled, working VC, I could fix the opaque HUDs in 2 sec.;)

If that is what you need, I can send you the latest modules from my PC today, but I have to go shopping first.

DaveS: Just ignore the library. Also, maybe you should check your compiler settings, it is possible that you have just "Multithreaded" as compilation output, which possibly the Express Version does not support (it might require the runtime libraries to be dynamically linked as DLL)
 
DaveS: Just ignore the library. Also, maybe you should check your compiler settings, it is possible that you have just "Multithreaded" as compilation output, which possibly the Express Version does not support (it might require the runtime libraries to be dynamically linked as DLL)
Problem solved was olved I changed the compilation setting from Multi-threaded to Multi-threaded DLL.

So thanks for puching me into the right direction.
 
Problem solved was olved I changed the compilation setting from Multi-threaded to Multi-threaded DLL.

So thanks for puching me into the right direction.

So, we should maybe create project settings for vcpro and vcexpress instead of all versions.

Donamy: What I wanted to ask, but never dared: Can you make a plasma boundary layer mesh for the Shuttle, for cuter reentry effects? just something, we can add to the visual, but don't make visible until reentry. I think it is something we can make as feature quickly and is on the wish list of many people.
 
Donamy: What I wanted to ask, but never dared: Can you make a plasma boundary layer mesh for the Shuttle, for cuter reentry effects? just something, we can add to the visual, but don't make visible until reentry. I think it is something we can make as feature quickly and is on the wish list of many people.
I believe he has already done that for Gazza's STS Payloads Pack v2.
 
Back
Top