Search results

Could you try running the scenario on a new install of Orbiter (+ Payload Manager)? The Pad isn't supposed to have a mesh, it is an invisible marker object (because Negishima uses the default non-vessel pads that come with Orbiter). But the barge was visible on the fresh install.

Did you install Kulch's PayloadManager to your main Orbiter folder? I tested it on a clean install, without PayloadManager I got the same problem as you did.

Which scenario are you talking about?

I just don't know how to set an offset point as a target in IMFD, that's all.

Is the delta-v required for corrections much more than what I had to do? But honestly, I do not actually know enough about IMFD to do that. I tried to ctrl+f "Offset" in the IMFD manual but I couldn't find it. Over a three-day transfer period, a vessel starting at L1 drifts about 10 kilometers...

With a target vessel preplaced at Earth-Moon Lagrange point 1 or 2 with Lagrangian points MFD, it is possible to get there using IMFD (and using RCS and docking HUD for corrections once you are a few thousand km away). Unfortunately, the trajectory wants to drift off and a few hundred m/s in...

So I just installed a RX 480 graphics card... ...and the Falcon 9 and M-III flyback and landing autopilots run flawlessly at 100x time acceleration.

I'm planning on doing a release sometime soon, but it won't have all the missions done yet.

M-III v0.1 now available! http://www.orbithangar.com/searchid.php?ID=6962 edit: why do I always forget something - updated to v0.1.1 fixing the missing M-III pad mesh

M-III is a medium/heavy launch vehicle featuring first-stage reuse capability through propulsive vertical landing on a pad near the launch site or a downrange landing platform (barge). All stages of the M-III launch vehicle have a 5.39-m diameter and use liquid methane/liquid oxygen rocket...

It didn't work. Adding libcmt.lib to ignored libraries got rid of the warning, but it still linked to the wrong location. Adding msvcrt.lib got rid of the errors related to OrbiterSoundSDK40.lib but instead gave me errors related to "M-III_stage02.obj" and "OLDNAMES.lib." Keep in mind that the...

I tried it, and it didn't work. Might the warning have anything to do with this? I don't know, because I used /NODEFAULTLIB and it only multiplied my problems.

Places like this tell me I should include the libraries under Linker->Input->Additional Dependencies but I already did that. It's just trying to link to the wrong location for some reason. I also tried copy-and-pasting that .lib (and also OrbiterSoundSDK40.h) to the "wrong" location, it still...

If you want to compare the performance of CPUs or graphics cards, I recommend UserBenchmark.

When I compile the code for the whole rocket/second stage in "debug mode," there are no errors. But when I compile it in "release mode" as I am supposed to, I get an LNK2001 error ("unresolved external symbol _fprintf") related to "line 1" of OrbiterSoundSDK40.lib. On closer inspection, it...

(it uses BrianJ's barge code, and the design is based on a special edition Sony XPERIA smartphone)

Sorry for the lack of updates, but I've been doing some tweaking over the past few weeks. (disclaimer: the screenshots below have increased contrast levels) Comparison of F9 and M-III first stages: Yes, there will be minor changes to the Negishima base .cfg. (make sure to...

Would it be possible to have high-resolution clouds like this KSP mod?

On a relatively fresh install of Orbiter (on my new PC) with the D3D9 client, there seems to be a graphical issue, seen at the top right corner of the image. Those pathways leading from the assembly building to the launch pads were part of a single rectangular mesh with transparent textures...

I am using Visual Studio 2015 Community (same as the last PC). Actually, when I downloaded Orbiter, the property sheets in OrbiterSDK\resources had the file extension .vsprops. So I got this error: and I had changed it to .props instead of .vsprops.