true... but in the other hand, if i don't, ppl won't be able to download it and fly right away without VC++
perhaps i should zip them up and include it separately
perhaps i should zip them up and include it separately
Precisely. The user should not need to delve into the intricates of software development just to use it, and the developer should no be expected to like the unnecessary bloat of intermediate and finalized files, or the push of personal files. Only include files that are generated by humans (such as source files), and files needed to guide one or more programs to the finalized product (such as project files, but NOT files like ones with the extensions *.ncb, *.suo and *.user in the specific case of MSVC projects, as they are not crucial and change periodically, further bloating the repository).true... but in the other hand, if i don't, ppl won't be able to download it and fly right away without VC++
perhaps i should zip them up and include it separately
Are you sure you installed everything needed? You seem to be missing the DLL (Modules/DGa2.dll if I'm not mistaken). Also, 'ERROR: DynamicPlanet' seems to be related to Orulex.i got the files and i selected the DGa2 launch scen. but it quits leaving this in the orbiter.log:
>>> ERROR: Could not load vessel module:
>>> [C:\Source\Orbiter\Vessel.cpp / 4982]
>>> ERROR: DGa2
>>> [C:\Source\Orbiter\Vessel.cpp / 4983]
>>> ERROR: No vessel class configuration file found for:
>>> ERROR: DynamicPlanet
>>> [C:\Source\Orbiter\Vessel.cpp / 248]
>>> TERMINATING <<<
whats the matter, i unzipped it fine... also when i try to spawn it in scnedit. it is nothing at all but just an invisible mesh.
whats wrong?
shame cause i was really looking forward to trying this baby out :-(
You need this: DGa2.dll. Put it on the Modules folder.whats the differnce between 'debug' mode and 'release' mode, and does that mean i just have to install visual studio and it should work?
Module compiled in debug mode has usually turned off all optimizations for the code that was generated by compiler, it's bigger, slower, and has either a reference to .pdb file that contains symbols used for debugging, or has those symbols embedded inside the file. It would also need other C/C++ runtime libraries if it's compiled dynamically (e.g. msvcm90d.dll, msvcp90d.dll, msvcr90d.dll and mspdb80.dll, for VC2008 that aren't distributed outside of VisualStudio/VisualC++ Express), or only one (e.g. mspdb80.dll) if static C/C++ libraries were used instead.whats the differnce between 'debug' mode and 'release' mode, and does that mean i just have to install visual studio and it should work?
I know it's a bit late to say this, but, AFAIK, that won't work unless you also post your RSA keypair (not recommended as you'd lose control over it). Take a look at GitHub pull requests. I think it should do what you want, but with more control over it.address is: [email protected]:Moach/DGa2.git
you'll (obviously) need git to commit any changes... (it's worth the steep-ish learning curve)
this way, anyone can make changes as they please, meaning the G42 will always be improving :thumbup:
Neither MSVC2005 nor MSVC2008 redistributable packages contain files that are needed:EDIT: On second thought, you'll also need MSVC 2005 redist. Google it if you don't have Orbiter BETA (it comes with it). Or MSVC 2008 redist...
They are a part of Visual Studio 2008 / Visual C++ 2008.It needs MSPDB80.DLL, MSVPD90D.dll and MSVCR90D.dll libraries.
Yeah, I didn't know it was compiled in debug mode :dry:.Neither MSVC2005 nor MSVC2008 redistributable packages contain files that are needed:
They are a part of Visual Studio 2008 / Visual C++ 2008.