I CAN NOT STOP TEASING MY WORK! SAY BYE BYE FALCON DANCE!
-
Sorry but i Just dont understand
First there is no more falcon dance since BMS is
One click installerFalcon dance comes from spx / f4UT era where many actions
Were necessary to installWhat we have now is considerably better than what we had with, say, SP4 or FF3, indeed. The BMS team did a nice work.
Still, however simple it is, the way updates must be installed now is quite unusual, so that it’s puzzling to many beginners. I understand why you chose to have separate folders for the setup and the game itself, but a more usual installation would certainly help beginners. -
First there is no more falcon dance since BMS is
One click installerBMS UI still requires Falcon Dance to Setup and Keep user’s Joystick Settings I thought.
Which should have avoided so many Flight simmers who are OK at learning Avionics but expect institutive UI for in-sim Setups, Sent a possible BMS users away.For instance:
Setting up controllers while connecting unused DX device and disconnect them for next launch mixes up callback mappings.
One of my friends had the following DeviceSorting.txt{0402044F-0000-0000-0000-504944564944} "Joystick - HOTAS Warthog" {C298046D-0000-0000-0000-504944564944} "Logicool Driving Force Pro USB" {0404044F-0000-0000-0000-504944564944} "Throttle - HOTAS Warthog" {100A04D8-0000-0000-0000-504944564944} "CH Pro Pedals Plus"
Yes, he had set up BMS kept “Logicool Driving Force Pro USB” connected maybe just after he played iRacing or AssetoCorsa.
When he launched BMS next day he found his Key Mappings for the Throttle has collapsed completely.Axis information would also disappear if you add any new DX device connected to PC.
Other my friend is also learning about any Aircraft he was interested in(He even is Aviation Maintenance Engineer).
He had been interested in F-16 Block50 too and tried to start learning them by BMS, but he said he doesn’t want setting up joystick again and again.I often asked by someone how to setup BMS/how to solve problems after setup their joysticks when I connected to TS.
They have no problem for learning DCS/FSX/X-PLANE/ARMA/Assetto Corsa/any other sim games but always meet something problem when playing BMS after a long time no flight.
I also have seen so many BMS beginners at Reddit/Twitter find setup hard to do and quit the sim even they are not first to play flight simulators like DCS, IL-2 or FSX.Secondly I don’t understand your launcher , you just replace the setup from UI with an external setup , what is the difference ?
Well, it is not just replacing existing launcher because…
No one will need to think about their device sorting order, joystick numbers plugged.
Those AXIS/KEY setups will be all saved per joysticks, and every time you launch BMS from my tool, this will generate proper joystick.cal/axismapping.dat/key file/callsign.popMy setup will remember joysticks setup with their product name/GUID so will not mix up even if device sort or numbers have been changed.
I developed this app as a launcher so that users will always launch BMS through my app.
It can auto generate/overwrite proper setup files for today’s device order before BMS find them changed and initialize his setup.Even if you setup BMS while connecting Logicool Driving Force Pro you don’t use for BMS, and next day you launch BMS without Driving Force Pro(but maybe with some another device you don’t care),
You will see key/axis setup still remains for BMS as the app has overwritten keyfile/axismapping.dat/joystick.cal to corresponds current device setups.Moreover, it has a more powerful function to easily/quickly setup controls.
In BMS UI you have to choose which Axis to assign from drop down list before you know which axis name corresponds to which joystick physical movement.
When I am to Radar Elevation Axis, I try each axis name of TQUSBAR R1 and find which axis works when I moved physical radar antenna knob.(It even garbles strings when using non-English Windows!)
As seen in my early development video, my app will catch joystick movement while opening Assignment Window.
So you just simply move joystick knobs to assign them.My app will have Category jump functions. And also highlighted HOTAS: STICK and THROTTLE category.
Anyone who opened pull-down list simply notices what he has to assign first is these callbacks, then can jump to them without long time scrolling to find the header.It will also have an ability to assign joystick button release, Invoke UP/DOWN which can not be done from stock BMS UI. (WIP here)
I also will add theater selector to the launcher so that you can change theater settings before launching BMS.
No need to launch BMS only to change theater, then relaunch again to fly those maps. -
About DX device id, I thought it has been fixed in Up3! (If not , at least it is in the future version)
-
You should use your talent to create a tool to replace lodeditor
It’s funny but when I saw the thread title and that it was chihirobelmo I automatically assumed it was a tool to easily install his skins as well. :mrgreen:
About DX device id, I thought it has been fixed in Up3! (If not , at least it is in the future version)
It was changed in Update 1 (BMS-Manual page 49)
-
It was changed in Update 1 (BMS-Manual page 49)
More than that.
Let’s say when someone setup FalconBMS first time, and his setup was like following.
{0402044F-0000-0000-0000-504944564944} "Joystick - HOTAS Warthog" {C298046D-0000-0000-0000-504944564944} "Logicool Driving Force Pro USB" {0404044F-0000-0000-0000-504944564944} "Throttle - HOTAS Warthog" {100A04D8-0000-0000-0000-504944564944} "CH Pro Pedals Plus"
BMS will assign DX0-31 to WARTHOG stick, 64-95 to WARTHOG throttle.
He finishes assigning whole essential HOTAS commands to Stick/Throttle.Next day he notices that he has been connected Driving Force Pro which is not needed for BMS.
He disconnects it and put away the stuff. Then he will notice no assignments has remained for Warthog Throttle.
Because In BMS he does not assign “Cursor Enable” for “Warthog Throttle DX0” but he assigns it for “DX64”.
He also sees BMS initialized whole axis setup.“Alternative Launcher” will remember settings like “Cursor Enable was assigned to Warthog Throttle DX0”.
If Warthog Throttle was 2nd joystick today it will generate the DeviceSorting.txt/key file and assign CE to DX32.{0402044F-0000-0000-0000-504944564944} "Joystick - HOTAS Warthog" {0404044F-0000-0000-0000-504944564944} "Throttle - HOTAS Warthog" {100A04D8-0000-0000-0000-504944564944} "CH Pro Pedals Plus"
If Warthog Throttle was 3rd joystick another day it will assign CE to DX64.
It also autogenerates joystick.cal and axismapping.dat binary files to keep setup that “Warthog Throttle Z axis is assigned to Throttle axis”.;)BTW why you thought I have made tool to install my skin while I have never made any skins for BMS yet:shock:
-
Well, keyfile writing is still WIP and I have to continue my development.
I just wanted to show my “teaser”
Because axis mapping generator is one of the biggest subjects of this project. It was so “Eureka” for me to accomplish this feature last night. -
Nice to see some ppl like you investing time and energy for free in BMS tools and software!
I admit that I won’t have any needs about this soft but probably other will. Thanks for them!
And if (?) on day you need inspiration and looking for an idea … Remember “LOD EDITOR” this is something that will be (directly or indirectly) profitable for the whole community!
Thank you again! Community needs more guys like you!
-
“Alternative Launcher” will remember settings like “Cursor Enable was assigned to Warthog Throttle DX0”.
If Warthog Throttle was 2nd joystick today it will generate the DeviceSorting.txt/key file and assign CE to DX32.If Warthog Throttle was 3rd joystick another day it will assign CE to DX64.
It also autogenerates joystick.cal and axismapping.dat binary files to keep setup that “Warthog Throttle Z axis is assigned to Throttle axis”.While Windows may change the sorting of your Game Controllers if you unplug/plug different controllers BMS 4.33 Update 1 and later will not. This means that even unplugging stuff and replugging it should not change the DX button numbers anymore*. BMS 4.33 U1 and later will also no longer overwrite your configuration, so axismapping.dat and joystick.cal files are no longer overwritten automatically if devices are in a different order in Windows.
So it should not matter what order the devices are in Windows anymore; BMS will keep the same order that you want in DeviceSorting.txt (*as long as you actually have the devices plugged in of course).
That said I think your software looks clean and user-friendly, which some may find easier to use to set up and maintain their controllers
BTW why you thought I have made tool to install my skin while I have never made any skins for BMS yet:shock:
Sorry, I must have mixed you up with someone else. It just shows how many talented people we have in this community.
-
So it should not matter what order the devices are in Windows anymore; BMS will keep the same order that you want in DeviceSorting.txt (*as long as you actually have the devices plugged in of course).
Yeah, If device numbers unchanged it doesn’t matter.
One of my concern was for someone who plugs/unplug devices daily playing through several sim games.When I was asked for help from the one of my friend, his DeviceSorting.txt was like following.
{001A045E-0000-0000-0000-504944564944} "SideWinder Precision Racing Wheel USB version 1.0" {001B045E-0000-0000-0000-504944564944} "SideWinder Force Feedback 2 Joystick" {0306057E-0000-0000-0000-504944564944} "Bluetooth HID Port" {FFFF044F-0000-0000-0000-504944564944} "Thrustmaster Combined" {0402044F-0000-0000-0000-504944564944} "Joystick - HOTAS Warthog" {0404044F-0000-0000-0000-504944564944} "Throttle - HOTAS Warthog" {100A04D8-0000-0000-0000-504944564944} "CH Pro Pedals Plus" {101A04D8-0000-0000-0000-504944564944} "CollectiveLever" {C298046D-0000-0000-0000-504944564944} "Logicool Driving Force Pro USB" {C2A8046D-0000-0000-0000-504944564944} "Logicool G940 Joystick" {03088888-0000-0000-0000-504944564944} "MotioninJoy Virtual Game Controller"
:shock::shock::shock:
No wonder his “Throttle - HOTAS Warthog” is 2nd/3rd/4th or 5th device depends on the day…
The concept of the project is to allow people quickly start to learn F-16 itself and concentrate on it.
UI itself should be clean, institutive, understandable without reading a paper as possible as it can be.Anyway thanks, Dee-Jay and Darkman for understanding
I just started learning C#/OOP for the development and starting to love coding. -
Anyway thanks, Dee-Jay and Darkman for understanding
I just started learning C#/OOP for the development and starting to love coding.Keep going on Chihirobelmo! … who knows … maybe one day you will be the one who will code the a replacement for LOD EDITOR … and later, a brand new vector UI map as a BMS coder (?)! This is how everything start!
-
This is the kind of program that I was looking for to install Jan Has Skins and before you guys jump all over me yes I know its just a matter of fallowing the simple install instructions but I cant tell you how many times I have found it not so simple / easy
this kind of program point click install would be great and time saving. -
You should use your talent to create a tool to replace lodeditor
I thought that was what the BMS Editor was for???
C9
-
@Cloud:
I thought that was what the BMS Editor was for???
C9
Nope. Lod Editor … not talking about F4Browse.
-
Nope. Lod Editor … not talking about F4Browse.
I said that because the BMS Editor already does some LE functions. Would make sense to turn it into a one App does all?!?
C9
-
Besides learning the airplane itself, setting up the controls is the #1 barrier to entry in BMS. A utility which is able to read (and edit) devicesorting.txt, axismapping.dat, *.key, Windows controller stack, etc. all at once and make sense of it in a single place goes a long way to helping understand the situation.
Is there any chance it could recognize SimHotasPinkyShift +256ing and 0x42 release contexts, especially the former? Even the BMS GUI doesn’t give feedback on +256ing and troubleshooting it is very difficult.
-
Besides learning the airplane itself, setting up the controls is the #1 barrier to entry in BMS. A utility which is able to read (and edit) devicesorting.txt, axismapping.dat, *.key, Windows controller stack, etc. all at once and make sense of it in a single place goes a long way to helping understand the situation.
Is there any chance it could recognize SimHotasPinkyShift +256ing and 0x42 release contexts, especially the former? Even the BMS GUI doesn’t give feedback on +256ing and troubleshooting it is very difficult.
Quite true, SimHotasPinkyShift is a great functionaly of BMS to use, but it´s very troublesome for newbies, and also for a lot a veterans who do not fully understand directx functionality or don´t have the time and will to learn it.
I thik it´s a great tool, highly welcome and keep it up Cloud9. :rolleyes:
-
@Cloud:
I said that because the BMS Editor already does some LE functions. Would make sense to turn it into a one App does all?!?
C9
Oky. Can’t tell you … I agree with you but maybe a question of time and resource …
Maybe one day … -
Well Lodeditor I’m sure it must have taken years to build up.
Is it’s code available to help a coder to understand some tricky parts?
Sure many will be tossed away but the main logic and file structure will remain the same.
Huge project… Maybe a team of coders could do it faster.
Like one the UI the other the functions.sent from my mi5 using Tapatalk
-
If the names are different between your utility and BMS it’s going to cause confusion, especially since FOV isn’t zoom (zoom is camera translation).
Thanks, I have fixed it.
Is there any chance it could recognize SimHotasPinkyShift +256ing and 0x42 release contexts, especially the former? Even the BMS GUI doesn’t give feedback on +256ing and troubleshooting it is very difficult.
It’s on the plan.
I still haven’t tried whole functions of LODeditor, only used it for Janhas Models and CCIP cockpit installation. What kind of changes are needed for the app?(oh, yet I didn’t mean I just get started with it.)
-
UI resize is the main issue.
New features for the BMS team. Like for instance for the hitbox to have the interface to CEUD (Create Edit Update Delete) records. Now each model has one hitbox, probably more will be needed.The CEUD will be needed in general to be able to clean records not needed.
Example: u create a record Parent and lods and u decide that you don’t want them anymore… well u can’t just erase it. u must replace it. Also I don’t know what happens when u alter the number of lods for a parent. Changes leave garbage? or update the records correctly?
I know that there is a batch function that erases empty and unused records but this is not the best way to go as it changes records index and might be a problem for future usage or compatibility with the BMS vanila (base) database.
Checking and cleaning a model would be nice if it could be done in a better way. Now doesn’t seem (to me) very effective.
Export to max format of a model would be a super wow feature, though I don’t think is doable. Maybe in FBX or OBJ format with the UVW and textures all packed in one place.
Also in many areas that are in the grey zone it would be nice to have some more info like balloons or text like what the hell this thing does. This can be done later on.Now the second biggest and u will be praised as a GOD feature would be a batch insert - update by comparing two sets of the 3d database and transfer things from the one to the other with just simple selection, like split in 2 frames left is source right is target. Spot and highlight the differences and provide the UI components and functions to tick select from left and transfer them to target. Manipulating conjunctions like hey man this parent record already exists… what to do replace or create new?
If replace do you want to just replace or the replaced one to be injected to a new record.
Also maybe something like a select multiple parents or lods and export them and then import them back. Or shift index numbers both parent and lods a few numbers down… Why? new version of BMS has new records. Those will overlap yours so u will have to alter them. also export and import and done nothing more to do would be perfect as now is in Falcon Editor. U export an objective u send it to a fellow theater dev and he just imports and he is done.
Having this for LE then the theater guys could make as many changes and then pass the two exports and the other guy will just import and be ready, nothing more to do regarding those two, FE and LE.UI and CEUD are the major ones. UI to work in a comfortable environment and CEUD to mainly be able to read the new 3d database format that probably BMS would like to alter and CEUD on this new database schema.
This means the whole database should be rebuild.
Just a few, nothing much, just a weekends work tops… :lol:
I have many many many other and am sure others will have too… Like grouping and taging of the nodes. For me useless, better do it in 3dsmax than LE. There is a tool for this why have it in LE?
Better and faster model manipulation in edit mode. Now it gives u hell. u must smell your fingers to find the nodes in the tree for complex models. It would be perfect to select from within the 3d view. well you can but it’s a pita as it is right now.Maybe a plugin to set properties from withing 3dsmax could be better than do it in LE. Don’t know if it’s doable. But if not those specific to LE (falcon database) properties must be isolated and manipulated accordingly.