Recent content by Redburne

Hi GB, thanks for updating Fly-By-Wire! You have my permission to upload your version to Orbit Hangar Mods and do whatever you want with the source code and the binaries. Oliver

The bugfix release 0.9.1 (for the trailing space issue) is up at OrbitHangar; this time, sources are included. Source documentation is minimal, but I'll try to answer questions ... ;)

I just checked, and unfortunately, the bundled sdl library is already the latest version. If I find another program using SDL for game controller handling, I'll check if it has the same problems with my X52. I may be doing something wrong, after all ... (but accessing the joystick axes in SDL is...

Fly-By-Wire (FBW) complements or replaces Orbiter's support for game controllers like joysticks and HOTAS (Hands On Throttle And Stick) systems like the Saitek X52 or Thrustmaster Cougar. With FBW, you can currently assign different axes on different game controllers to control main engine...

The core functionality is written in Delphi 6/Object Pascal. A small Visual Studio/C++ DLL interfaces with Orbiter.

Just some quick notes: HiPotOk1978: As posted in the other thread, the Saitek Rudder Pedal problem is probably due to problems in the underlying SDL library. I'll check if the latest SDL libs cure it. Robb: Source code release was my intention from the start. I'll probably add the sources to...

It is indeed very likely that the problem is related to the Rot2 issue with the X52. I'm using the SDL library to access the joysticks, and I supect it is the culprit in this case. Time permitting, I'll recompile FBW with the latest SDL library before I put the latest fix on OH.

Guess I should have read Driver8's message of 2009-02-11 more carefully, as it already describes the problem quite accurately. If someone would be so kind and test the new core dll (it goes in the <Orbiter>\Modules\FlyByWire folder): http://oliverpieper.de/orbiter/FlyByWireCore090725.zip I...

Hi guys! Sorry for the long radio blackout. My interest in Orbiter is currently close to zero, and this is unlikely to change in the forseeable future. But I do consider the "trailing space issue" a serious problem and will take a look at it, this weekend!

Good to know it's working for you, now! :) Did you transplant FBW from one installation to another? Normally, extracting from the ZIP file should create the entire folder structure. But as the "current" folder is empty, some unzippers might skip it altogether. I could put dummy files in empty...

It's an expensive way to shirk my responsibilities as an add-on developer, but it works nicely ... :P

Hi Hielor, there definitely is an issue with the thrust settings at program start. It's not always 50%, but I sometimes get settings of about 2 to 5 percent. Not much of a problem when I'm on the ground (where I usually start my test runs), but very annoying on orbit. I hope it goes away when...

My current understanding of the situation: All physical keyboards, wether they are showing French, English or German layouts, are identical. They just differ in the labels on the keys. If you press the key to the right of the CAPS_LOCK key (which is labled Q on some keyboards, A on others)...

Strange, as I have the same configuration as you. Did you make sure (by entering text in a MFD) that Q and A are really switched? Please be aware that switching keyboard layouts is a bit tricky in WinXP. I've enabled multiple layouts (DE, EN, FR) and can switch them in the Windows task bar (in...

Anyone can change the Windows keyboard layout to French and test this, by the way. Bonus points for style, if you switch the physical keys as well ... ;) Looks like Orbiter does indeed switch CTRL-Q around to whichever key happens to function as "Q" at the moment. This is clearly contradicting...