I'mjust now getting this addon set up and caught up with. I'm having a problem however, It seems that the spacecraft module is ignoring any changes I make to the ini files. I wanted to make the PMA2 dock heads up for the crew dragon, with consideration to the conformal solar arrays.
Yes I know...
Look in your main orbiter folder for the subfolder OrbiterSDK/Doc, for some reference materials, and check the developers and tutorials subforums for more specific help, especially in getting Visual Studio Express (now community, also full Visual Studio if you have or can afford it) set up to...
there is a good bit of hands on flying with the falcon 9/cargo dragon scenarios if you start with the launch scenario and don't skip to the approaching ISS scenario. And it is pretty challenging if you do it the way they do it IRL. Which is..... at some point as your lower orbit position...
well It's kind of good to know that it isn't just me, the Trim does nothing at all for me either, is there an archive available where I can get an older version that DOES work?
ETA: I downloaded the zip provided up thread and it works fine for my present needs.... station keeping the dragon and...
You can't use the autopilot, at least not for the 3rd stage, you need to fly the third stage so it ends up putting the Briz in a very high ballistic trajectory, Apoapsis between 300 and 400 km iirc. then burn the briz straight at the velocity vector, depending on the payload you may just make...
Yes that helped, but only that it got me looking in the right places to figure it out, it turned out I had to add them in properties - linker - Input - Additional dependencies.
The library files still don't show up in external dependencies, but it does compile without errors now.
1) not sure about the SDK files, I just did the one download and unzipped into orbiter, activated the module in launchpad and it works.
2) They are both in my OrbiterSDK\lib folder and I pointed to that folder in the project properties. Should I copy them to my project folder as well? And the...
I had a hunch and found and dl-ed a copy of 2010... got none of the slew of warnings I had with 2017, however, still the same errors.... here they are:
1>f9_v12_stg2.obj : error LNK2019: unresolved external symbol "bool __cdecl gcEnabled(void)" (?gcEnabled@@YA_NXZ) referenced in function...
well it works fine if I quit and come back to the current scenario. But I have yet to get the references to show (for canaveral on earth anyway) if I run orbiter continuously from orbit insertion.
oops, well if you got it back from there and base sync worked for canaveral without shifting, I guess it's something weird going on with my system. let me try to upload the after earth orbit insertion scenario .... then try it again myself since I rebooted, and got glideslope working right after...
Well now that I am trying an earlier dated scenario where Base Sync works, Glideslope doesn't work. I get no reference data, starting with range and azimuth, trying to approach canaveral rnwy 33 or 15, tried each GS in confg, doesn't matter.
I tried repairing the vc 2015 redist and the MSVC++...
Nope, that is not the problem, the mfd actually thinks the base suddenly shifts 90 degrees to the West, I am not misinterpreting the screen, that orbit I was in passes within 15 km of cape canaveral, there is no "better orbit" 18 hours later that the MFD would suddenly decide to switch to 900...
the scenario is in an XR2 just returned on the moon, already lined up for deorbit to canaveral after one more orbit.
To reproduce the problem just bring up base sync with or without linking to glideslope, set up cape canaveral as the target, and watch it's position shift 90 degrees to the west...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.