Search results

More than a year has passed and whoops there it is: HoverMFD 1.1.0 :) I didn't manage to get deeper into the tailsitter topic in this version, but somewhere in my mind the ideas may grow up to some later development. You should try the new "Travel" page for AP control. You'll also find some...

Thank you for your quick response. Ok, that is is a good reason. I'm using your scenario file where it is a vessel of class XR5VanguardTest, so it has your attachment point defined. I checked it within sim, it is a vessel of that class. I also checked the attachment point is there (attachment...

Useful thing :) More useful would it be to be compiled in release config, so you don't need to find a msvcr100d.dll anywhere and pollute your system ;)

I very like the idea of this. Any news? I can't find a release in OH. Only got the alpha 0.05 from this thread. I can start the test scenario with the tug and a XR5 at Wideawake. I can drive forward and backward, attach a towbar front or back. But what then? I must have missed some important...

Thank you for your quick response, but I don't see any hint :hmm: The question how to determine a time to burn by distance instead of time I solved already for my constant-deceleration-stage. There I aimed a speed of v = sqrt(2*s*F/m) which results in constant deceleration. Here I know how to...

Hi guys, I got stuck with some maths and maybe someone here can help me. I'm coding an AP to approach a certain target. After the main stage of linear deceleration I have defined a point for the very last much smoother approach. Here I say my aimed speed v is a linear function of the distance...

Ah you finally made it to orbithangar :thumbup: I like the rotor functions now, although the disc design could start somewhat later, like Urwumpe said before. The altitude is limited but you can get as much vertical speed near ground to overshoot that limit alot. Later you fall down and just...

Next version 1.1.0 (not coming real soon) checks engines by looping through all standard and user defined thruster groups. Depending on thruster direction they are used as needed. Maybe main will be used as hover, pod as retro or whatever. Also up to 2 engines are supported for one direction...

Yes I see, thank you. For each single thruster I can get the thrust by thruster handle and so leave the ENGINE_X world behind me. ---------- Post added at 18:33 ---------- Previous post was at 18:08 ---------- Hmm :hmm: now trying to code I can't see any link between each individual thruster...

I want to support various engine setups in my AP, tail sitters, thruster pads and so on. My idea was to loop through all thruster groups and then check the vectors which one would fit to my needs. So maybe I can use the main engine in fact but treat it like a hover engine for all calculations...

Here's one MFD developer and I already thoght about problems like this. First I'm not really shure what exactly is a standard tail sitter. A standard z-aligned main engine, but no hover engine, so main engine has to be used for landing / hovering purposes A main engine that is not aligned in...

With that version and full vertical thrust I reach about 4200m altitude and then fall down (still full thrust) to 170m. Raising slowly I reach the point where thrust equals gravity at 2500m. For the horizontal speed I easily got 1400m/s at an altitude of 500m. Then I had to reduce pitch...

I just tried the dolphin(edit: the dolphin1.zip). Very nice to have some variations of heli to fly :thumbup: Flight characteristics seem to be still the same. I can't see if K is pressed unless I use some MFD that shows max hover thrust. One would expect to see rotors starting. I easyly reached...

At first its funny to see that the free world is such small and the combo of orbiter, celestia and flightgear is the same one I am using :cheers: Then talking about traveling to other stars (and what else do you need simulation more than one system at same time) I have to say this is far far...

Is there a newer version than "seakingpm.zip" from 24.08.? When your realistic calculations do work you should really put this to orbithangar. In case of the calculations you shoul try to keep it simple for the first "stable" version and enlarge realism in later version. It would be sad if you...

I don't know what would be physically correct but when the atm pressure is a factor the alt limit would be solved (and moon problem also). For me personally a simple calculation would be nice enough.

You have to write such a method I called SetSomeMemberProperty() void MyClass::SetSomeMemberProperty(char *str) { double data; if(sscanf_s(str, "%lf",&data) == 1) { // do your attachment stuff I'm not familiar with // and use "data" as the input } } My comments for current...

You need a buffer to write into. In my MFD project I used a global variable in my module because MFD classes are created and destroyed much too often. Within a vessel there may be no such problem and this could be a normal member. char inputstr[80]; Then you need a callback function like this...

Try F8 and switch to generic cockpit for better MFD readability. If you need some vessel-specific display or buttons, switch back to the panel view.

When I was noob I didn't like the DGIV because the only things someone could ever miss in DGIV: - no virtual cockpit - no such docking-light-switch the stock DG has But then I tried DGIV and with practice I liked it because of - much more functions and nice little buttons - autopilots - cargo...