Seriously impressed!
-
I would recommend uploading the documentation to Google Drive or some other cloud based storage so you can access them on a tablet or via web browser from anywhere
https://www.benchmarksims.org/forum/showthread.php?23315-BMS-4-33-Documentation
thanks for the recommendation, but the docs are available in paper from lulu, in pdf from the link above and they are as well placed in your doc folder
I could add them to a dozen other media, but ppl will still look for them anyway.
So i believe the 3 ways offered currently are already enough and hard to maintain for the doc team !
btw, 2 of the 3 way already offered allow PDF and tablet reading, so you are covered - you don’t need google drive -
I talked my wife into letting me ‘borrow’ our 35" security monitor to be able to see better. I still have my w1907 monitor as well.
I have put all (Ithink) the manuals on both of my tablets. I just emailed them to myself so I would have the same on all devices.One issue I see already is that the resolutions are going to give me an issue the 35" will work for my main screen til we get our new TV, then I will have a 55" flight monitor.
I’m not a programmer by any means so I will take all the advice I can get. To destress I tried a flight in F4AF, but I can’t control what screen it comes up on. Do you, or anyone reading this know how to control what screen I want to use?
If I could get the HDMI cable in the plug in on my video card I could have 3 monitors, basically having 2 19" MFD’s.Is there someone I can pick thier brain on this aas I have many questions and I’m embarrased about the title of this thread.
-
I’m fairly certain the moderators would allow you to start a new topic.
-
Many, many years ago I used the Falcon 4.0. But the resolution was low.
My Thrustmaster F22 Pro, and the TQS throttle and the FCLS foot pedals I have sold, because with the newer faster computers, without DOS, it is hard calibrating them, with the 25 pins plug.
But now with the BMS it is a feast again. It is really an enormous improvement. I have bought again a Thrustmaster joystick.
The original Falcon4.0 CD got lost in a fire, but I could download the version now. Luckily I still have the very big manual.
On the backside it has printed Microprose.
I know a lot of flight sims software (my first was on the Sinclair 48K Spectrum) but I never saw a Falcon by Atari.
I was the first who imported the Sublogic Flight Simulator for the Commodore 64 in the Netherlands.
Looking at Microsoft Flight Simulator FSX and the X-Plane 10.50, the Falcon BMS 4.33 is an tremendous good sim. A very good well-done job! -
No, but microprose did not survive long after F4.0 was released. Their IP was sold off, and for a while Atari was the owner of the F4.0 IP. Recently this has changed, and now Retrosim is the owner of the IP. Folks have been using Tommo interchangeably, as Tommo owns Retrosim.
-
I’m embarrased about the title of this thread.
It is nice to see a FNG that took the responses to the OP in stride and noticed that you were the one in error. That has been the bane of many a FNG is to get frustrated and instead of asking for help or asking what you are doing wrong to lash out and blame the sim. Have seen that happen SO many times and it gets old since we can just look at the post and start counting up the ways in which the poster FUBAR’d.
To any FNGs reading this post PLEASE don’t attempt to take out your frustrations in a post like the first one as you will get hammered and rightfully so. ASK for help and it gets given. Blame the sim for your lack of knowledge? I’m getting out the popcorn.
-
I think I was just having a bad day. I spent too long in the military with multiple deployments to not recognize when I don’t know something. As I understand my lack of knowledge on this sim, I am trying to get instructions and help from this community.
I have the manuals and have printed out the Falcon BMS Keyboard Layout (QWERTY/US Int.) but I’m not sure where to find the the .pr0 file that goes with the layout. I tried the X52.pr0 profile and didn’t see anything in it.
And yes, I have been looking through the forums.
I’m not a programmer and I don’t understand the DX file system. It sounds like it is supposed to be easy, but I don’t understand running the file lines into the DX numbers.
Since a lot of the comments I’m seeing are a couple years old I’m not sure if I can get reply’.I have also gone back to flying F4 while I’m doing my studying BMS Falcon. I do know I need a lot more flight hours. I see most of the senior members have been on this for years and with the vids I’ve watched are great flying.
I looked at the BMS Viperdrivers and realized how much I really, really don’t know.I will continue to strive to be a sim pilot sometime down the line, but I do need help.
-
….
I have the manuals and have printed out the Falcon BMS Keyboard Layout (QWERTY/US Int.) but I’m not sure where to find the the .pr0 file that goes with the layout. I tried the X52.pr0 profile and didn’t see anything in it.
And yes, I have been looking through the forums.
I’m not a programmer and I don’t understand the DX file system. It sounds like it is supposed to be easy, but I don’t understand running the file lines into the DX numbers.
Since a lot of the comments I’m seeing are a couple years old I’m not sure if I can get reply’. …John, it sounds like you’re confusing two different things that may, or may not, work together depending how you’re setting up your HOTAS and Keyboard. The default keyboard layout IS a DX layout …. keys are mapped directly to BMS commands and will work without a Saitek pr0 file.
The *.pr0 file is a Saitek profile file. It is, usually, user created. It basically acts as an interface between and input device (like a joystick) and a program (like BMS) to virtually press keys on the keyboard. It is a keyboard emulation program. For instance, you pull the trigger, the Saitek profile sees that ‘pull trigger = press F’ (what equals what is the info in pr0 file) so it sends a keyboard ‘F’ to BMS. The BMS keyboard layout has the ‘Fire Gun’ command associated with the ‘F’ key and the gun fires.
With DX you ‘cut out the middle man’. You link the trigger directly to the ‘Fire Gun’ command. Pull the trigger, the gun fires. No 3rd party key emulator; no virtual key press on the keyboard.
In any case, a command (called a ‘callback’) has to associated with an action (pressing a keyboard key or a HOTAS button/switch). This is the actual, proper ‘Fire Gun’ callback: SimTriggerSecondDetent.
Depending on your need, there can be a time where you ‘mix and match’ Saitek programming (pr0 file) with BMS programming (DX). The kinds of setups run the gamut from nearly 100% Saitek to run the HOTAS to 100% DX to run the HOTAS … and many mixed variations in between. It depends on personal need and preferences.
All of this together … the association of BMS commands to the HOTAS and the keyboard … comprise your keyfile.
What keyfile are you currently using and have you made or downloaded a pr0 file? I strongly recommend going with a keyfile that someone has made and shared. Start with that as a basis for customization. There should be several X52 keyfiles available.
-
It is worthwhile to appreciate the entire chain from button to result which has a few links. Some middle links in the chain are configurable by joystick software, device sorting, or the .key file.
For example:
Press Button A
Saitek SST Software produces a keyboard “B” keystroke
BMS user’s key file interprets a “B” keystroke as being callback SimEjectResult: Button A = SimEject
A different example:
Press Button A
Saitek drivers or SST assign a DirectX button output
BMS modifies the button number based on which device number it is to produce a globally unique button number
BMS user’s key file interprets a button number (e.g. 56) to the callback SimEjectResult: Button A = SimEject
The major lesson is that the SST (or any joystick) software shapes the output and the .key file translates that output into sim action. They cooperate and are made to match so that what one is throwing the other is catching. “When I press this button, give this output” says the joystick software and “when I see this joystick output, I will trigger this sim action” says the key file. There exist .pr0 files and .key files that come as matching sets which should just work out of the box.
The one caveat to this is if the key file is expecting your joystick to be buttons 1-32 and they are 33-64 or 65-96 that just means BMS is taking your joystick as device #2 or #3 or #4. Devices are assigned blocks of 32 buttons. The devicesorting.txt file prioritizes device number assignments simply by the order top-to-bottom the devices are listed.
Now you absolutely don’t have to understand the key file format unless you get into the more advanced tweaking. To modify which input is associated with a command you simply highlight the callback in the list you want to set then press the joystick button. This works both for keystroke-emulation output or DirectX button output. Highlight, press, highlight, press, highlight, press… that’s it.
-
It is worthwhile to appreciate the entire chain from button to result which has a few links. Some middle links in the chain are configurable by joystick software, device sorting, or the .key file.
For example:
Press Button A
Saitek SST Software produces a keyboard “B” keystroke
BMS user’s key file interprets a “B” keystroke as being callback SimEjectResult: Button A = SimEject
A different example:
Press Button A
Saitek drivers or SST assign a DirectX button output
BMS modifies the button number based on which device number it is to produce a globally unique button number
BMS user’s key file interprets a button number (e.g. 56) to the callback SimEjectResult: Button A = SimEject
The major lesson is that the SST (or any joystick) software shapes the output and the .key file translates that output into sim action. They cooperate and are made to match so that what one is throwing the other is catching. “When I press this button, give this output” says the joystick software and “when I see this joystick output, I will trigger this sim action” says the key file. There exist .pr0 files and .key files that come as matching sets which should just work out of the box.
The one caveat to this is if the key file is expecting your joystick to be buttons 1-32 and they are 33-64 or 65-96 that just means BMS is taking your joystick as device #2 or #3 or #4. Devices are assigned blocks of 32 buttons. The devicesorting.txt file prioritizes device number assignments simply by the order top-to-bottom the devices are listed.
Now you absolutely don’t have to understand the key file format unless you get into the more advanced tweaking. To modify which input is associated with a command you simply highlight the callback in the list you want to set then press the joystick button. This works both for keystroke-emulation output or DirectX button output. Highlight, press, highlight, press, highlight, press… that’s it.
Or you just follow my advice of a 20 years falcon simmer and developer and you never ever touch your keystroke in BMS
Assuming you have a joystick with a programming software , the job must be done in your external software so that the correspondence between you buttons and the BMS keyfile matches . This is the purpose of those software : avoid changing the game default keystroke.
Imagine keystroke of BMS beeing Non editable and program your joystick like if it was .
-
……I am not using this as an excuse, but to let you know a small bit about me. I was injured in an IED blast in May 2007 in Ramadi, Iraq…
If somebody already said it then my apologies, but thank you for your sacrifice sir, wishing you well in your recovery.
As to BMS then once you are comfortable with your HOTAS and controls setup then there are some excellent training videos by Krause (I am sure that he did not read all the posts before his reply) but the Brits can make movies too and Supanova has created some superb training videos which are more recent and BMS 4.33 centric - check out his YouTube channel and I am sure that you will not be disappointed
-
Or you just follow my advice of a 20 years falcon simmer and developer and you never ever touch your keystroke in BMS
No thanks I want a good control config instead
-
No thanks I want a good control config instead
You don’t need to touch anything to get the real f16 Hotas configuration
Why would you need more ? And besides , please explain why do you need to touch the keystroke instead of programming your joystick ? Please explain because after all those years I still don’t get it
-
You don’t need to touch anything to get the real f16 Hotas configuration
Why would you need more ? And besides , please explain why do you need to touch the keystroke instead of programming your joystick ? Please explain because after all those years I still don’t get it
If I may, for my part, it’s a matter of habit with sims I’ve been playing for 20 years. A command list that was responding to revamp straight from the UI was the quickest and easiest way to obtain what I needed, especially when I wanted to go back to my pdf and virtual cockpit as soon as I could. I started to build my X52 HOTAS settings from that point and reached a satisfactory setup in the end. If there is a flaw in the method that will harm my experience, then it is the thing that I don’t get, just as well as many others, obviously. But I wouldn’t want you to rewrite what you already elaborated earlier here, I have read it already and it must be just me.
-
You don’t need to touch anything to get the real f16 Hotas configuration
Why would you need more ? And besides , please explain why do you need to touch the keystroke instead of programming your joystick ? Please explain because after all those years I still don’t get it
It should be well-known the benefits of not using keystroke emulation. I can give examples:
1. I don’t want if a cat jumps on my keyboard that my landing gear can ever come down.
2. I wanted to make “F” press the F-ACK button.
3. If I am typing in chat and I press uncage button I don’t want it to put “U” in my message.
4. I want to use the SimHotasPinkyShift function.
5. I want to press UHF transmit and TMS up at the same time.Middleman keyboard joystick emulation might give fast results but it has drawbacks: key collisions, taking up the keyboard from other functions, able to accidentally be pressed on keyboard. Keystroke emulation without editing the default key file is acceptable for most people with most desires most of the time. But editing the key file and/or using DirectX direct binding in places simply allows you to do more things than if you forbid yourself from doing it.
-
You don’t need to touch anything to get the real f16 Hotas configuration ….
True only in the case where your HOTAS is a Cougar (or WH/Cougar TQS combo). In MANY other common cases, it’s not a 1:1 hat/button match to the F16 HOTAS so you MUST create an alternate configuration to accommodate the F16 HOTAS functions.
-
True only in the case where your HOTAS is a Cougar (or WH/Cougar TQS combo). In MANY other common cases, it’s not a 1:1 hat/button match to the F16 HOTAS so you MUST create an alternate configuration to accommodate the F16 HOTAS functions.
I think you are taking what Mav said out of context. He is saying that everything on the F-16 HOTAS is already mapped as a function in the keyfile.
-
Thats not what he said. He said you need never touch the keystrokes file, and you should set everything in your joystick programming.
Which is of course a load of bunk. You should set the keystrokes file to use directx presses, amd that is only going to work properly if your interface to the sim is a single, solitary cougar.
-
Thats not what he said. He said you need never touch the keystrokes file, and you should set everything in your joystick programming.
Which is true. You absolutely can program everything in your joystick programming software, as long as your joystick is complex enough to have additional software.
Which is of course a load of bunk.
Im not sure why you feel the need to demean someones opinion… Im certain there is a rule about that someplace…
You should set the keystrokes file to use directx presses, amd that is only going to work properly if your interface to the sim is a single, solitary cougar.
This is also a totally acceptable way of doing things. But it is also your opinion on if it is the best way or not.
Or you just follow my advice of a 20 years falcon simmer and developer and you never ever touch your keystroke in BMS
Notice he says that it is his advice… Decide how you want to do it, but lets not bash people for giving an opinion
-
Im not bashing people. I have the greatest respect for Mav. After all, he is responsible for the flight model in my favorite sim - which is my favorite in large part due to its flight model.
I am absolutely demeaning that opinion however. A close reading of the forum rules indicates that rule 7 can apply here, to every single post made on this forum, should you so wish. So you are correct - there is a rule about that, someplace.
I will concede it is certainly my opinion (one which is shared, but it is absolutely my opinion nonetheless).