Search results

You may have more luck when looking at a function that is actually implemented in that DLL. VESSEL2::clbkPostStep is not. That is implemented in orbiter.exe. So all you see here is the function entry point, which, I assume, is linked into the DLL vla orbiter.lib. Curiously, this seems to include...

You mean we are now in sync because you replaced your own calculation with mine? :blink: I am flattered, but as long as the 11% difference you reported isn't explained, there is no guarantee that my code is any better than yours, so there is still work to be done. As far as I can tell, both...

So, was the discrepancy just down to a difference in radius? It sounded quite significant.

Let me just quickly declassify this for you. Here is the relevant VOR/VTOL MFD code: void Orthodome (double lng1, double lat1, double lng2, double lat2, double &dist, double &dir) { double A = lng2-lng1; double dlng = fabs(A); double dlat = fabs(lat2-lat1); if (dlat < 1e-14) { dist =...

Good news. It may be that the conflict just happened in the [Current state] scenario, and that got overwritten with a valid one now. Usually my deployment script set the [Current state] scenario to a defined default one, but it looks like that didn't happen recently, and the scenario just...

Also, for the cases where it doesn't fail, does it give you the expected result? I am a bit concerned about those lines: dis = (dis)*DEG; dis = dis * 6371; Is that making the approximation sin(x) ~ x (i.e. small distances)? Even then, converting the central angle distance to degrees rings...

The only function that could potentially throw an error I can see here is the acos. Did you check that the input is valid (range [-1,1])? Even if your calculation of the argument is mathematically correct, there is always the possibility of rounding errors. Would that make a difference here...

Let me know what you find. If the problem arose in the [Current scenario] then that isn't unexpected. If it happened in the stock Delta-glider\Brighton Beach scenario, that would be a bit more worrying. To my knowledge, I haven't changed that file in a long time, so checking it out shouldn't...

I'm pretty sure that <<<<<<< .mine isn't a vessel class name, but an SVN conflict flag :lol: Did you get any conflict warnings during the SVN update? Look at the scenario you are trying to run. There will be one or several patterns like this: <<<<<<< .mine [some stuff] ======== [some other...

Ok, I've uploaded a new commit now that incorporates the framework for the documentation of the vessel-specific Lua extensions (DeltaGlider only so far). A few things: * After some more thought, I have changed my mind about the separate dummy Lua file for documentation. I have added the...

Lua supports file operations through the methods in the 'io' table. This is described in the Lua manual.

Sorry for the late response. I've been living without internet at home for the last week, and just got reconnected today. It's frightening when you realise how much you rely on it just to do something trivial like looking up ldoc format documentation :huh: Anyway, back in business. I'll have a...

Fair enough, but this appears to be no quadcopter at all, but a more conventional twin-rotor helicopter. So the control mechanisms coded by my quadcopter sample won't help you much there.

The concept is the same surely. You need to calculate the thrust force as a function of RPM anyway, so you factor the rotor geometry in there. Obviously, arranging two rotors on top of each other provides less than twice the thrust of a single rotor. Also, if the rotors have opposite spin...

Thanks for volunteering on writing documentation! It's much appreciated. Maybe a separate .lua document containing only the documentation in ldoc format would be easiest, since I could then just automatically run ldoc over it as part of the build process. The only disadvantage is that for any...

Not having access to a real-life drone myself, I have a question about how the controls generally work. Specifically, are the pitch and roll controls vessel-relative (e.g. pushing the pitch control stick pitches the the drone down with respect to its own forward direction) or operator-relative...

The missing mesh and config files should be fixed in the latest beta. It also adds a Lua interface for accessing some of the autopilot modes. No documentation yet, so you'll have to check the code to see what is available and how to call it.

http://orbit.medphys.ucl.ac.uk/betainstall.html

I have uploaded a new Orbiter commit that includes the Quadcopter implementation (in Orbitersdk/samples/Vessel/Quadcopter). It's work in progress, but should be enough to play with the code. There are currently three control loops implemented: vertical speed (controlled by manual throttle...

Here is another option: Since the quadcopter simulation problem had me intrigued, I have written a plugin for a generic quadcopter. It will be included in the next beta commit, whenever I find time to upload it. You are welcome to adapt the code for your Titan drone.Mine is currently...