Some 4.33 issues…
-
Just like in real only three indications off, closed, open
-
I’ve copied and paste my old key file after the last row of “bms full” key file (opened with notepad) and everything works smooth and clean
-
No, definitely not. I am not saying you should edit the old key file. For people who used Keystrokes.key with 4.32 (like me), when you install 4.33 none of your controller profiles will work because keystrokes.key is gone in 4.33, and it will takes some time to rebuild everything for the new key files. So what some of us have done is take the keystrokes.key file from 4.32 and use in 4.33 just to get flying. I am not recommending you edit old key files from 4.32 in 4.33. If you use 4 or 5 controllers like me it will take more than a day to build all the new profiles.
It seems you are following the dev forum not at a regular basis.
Even Boxer, with a full cockpit setup, got everything to work within 2 hours
-
It seems you are following the dev forum not at a regular basis.
Even Boxer, with a full cockpit setup, got everything to work within 2 hours
I am clearly not Boxer nor as tech savvy about key files :D.
The fact I have been using keystrokes.key since Open Falcon should tell you that :D.
-
Yes, I just discovered. I have to relearn everything from 0. Even the 10+ year usual keyboard settings are gone. I simply do not know what keymap should be used. It is not explained BMS Keyboard Layout (US Int).pdf correspods which ingame layout setting.
molni,
everything is explained in the …Docs/Key Files & Input/… subfolder.You can adopt your old key file for now but will most likely be screwed in the future. So better learn the new Stuff or try using the keyfile editor.
-
I am clearly not Boxer nor as tech savvy about key files :D.
The fact I have been using keystrokes.key since Open Falcon should tell you that :D.
I didn’t know you have issues with that.
If you need help you know where to find me… -
This is also a good point … New key map is just completely intuitive compared to what we had before. And includes new commends and features not present in older .key
If you are using you old .key just for quick test today/tonight, it is okay, … I HIGHLY recomends to switch as soon as possible to the new .key choosing the one which fit with your needs. It is not so difficult …
-
I followed the same path as Demo for quite a while.
Using my old key file from OF or even before.
Adding new call backs little by little as they came along.
But it soon became clear that it was time to just sit down and get r done.Much easier than I though too.
-
The main point why using the new key files as a basis is a good idea (or converting the old ones to new standards with the key file editor or manually) is not what has happened between 4.32 and 4.33 but what will happen in the future.
-
100% with Kolbe! … Thiking also about speaking the “same language” for support stuff -> thinking about “newbies” asking for helps
-
As the Warthog key editor file is incomplete and still a wip e.g simhotaspinky (no formula)
What information is required?Willing to help but I do work shifts so my time is limited, PM me if required.
-
As the Warthog key editor file is incomplete and still a wip e.g simhotaspinky (no formula)
What information is required?Willing to help but I do work shifts so my time is limited, PM me if required.
The Worthog is in so far wip as I do not own one and can’t test it to fully extent.
Can you explain the “simhotaspinky (no formula)” a bit more?
Just checked the file and everything seems to be fine on my end.Please give me a reminder via pm or just post here.
-
The new keyfiles organisation is a given, but like demo i still use my old OF custom keyfile i updated over time with new callbacks… If you know what you are doing, using old keyfile is not a problem. Just look for the new callbacks and add them and remove the old outdated ones. You may loose the formatting when you do that from the ui so it is not advised.
Bottom line, custom keyfile works very well, just make sure you update them bit by bits. -
First off I payed my respects by thanking.
Once again words r not enough to express the gratitude and admiration.
But let’s get to work…
with vanila 4.33 just the softth dll for the 3 monitors nothing else. No log no key files no theaters no nothing.
64bit crashes before UI loads, all the times, with no crash log files. shows a black window:
First test flight in pit the mouse cursor was not displaying. At some point something was about to show and vanished right away. On second test flight the mouse cursor was there and functioning.
In pit when you look all the way back the icp keyboard is there and functioning just not displaying. if you move the mouse you see the cursor changes I was able to turn off the HUD brightness from there.
changed multisambling from 3 to 2 to see how the FPS goes the mission load got stack on the second pie and never loaded. The disk was working like crazy and after a coffee preparation and some minutes waiting for it bms just vanished without any crash message, nor any crash log.
in keyfile manual:
BMS Keystrokes - Defaults.pdf
says : OTWToggleFrameRate yes none F yes SIM: Display Frame Rate - Toggle Frame Rate
which points that pressing the F key in pit will display my fps… but in the commands listing in the UI the fps command says it’s Alt c f.
Probably same goes for the rest bellow.Now I just seen says some lines bellow:
CommandsSetKeyCombo yes Alt C no SIM: Key Combination Keys (KeyCombo) KeyCombowhich kinda at first tells me it’s a declaration of a keystroke and not a definition of combined keys, that works with other key commands… I got it but a newb I don’t think so.
Just a kind suggestion the line CommandsSetKeyCombo yes Alt C no SIM: Key Combination Keys (KeyCombo) KeyCombo could be in the beginning of the doc so that reader gets the point and maybe repeated in the beginning of every section it has such a use.wow on Kolbe for the effort on redoing and rewriting all those guides. Thanx m8.
-
deactivate video from config options if you run 64 bits ?
-
@Red:
deactivate video from config options if you run 64 bits ?
if you mean display intro movie? yes I did try that. no change.
Oh I forgot how amazed I got that even with 14 fps on inclement weather the sim was flawless and stable and super fluid. no hickups like I had 30+ fps… wow RESPECT.
And wow on the Falcon Editor… many many things are there …
-
Damn I must be damned some how… or I need a OS restart…
I just can’t reboot right now as I upload the 4.33 setup file to Mediafire for guys to have an alternative than torrent.
First time the avionics configuration worked fine… I did some test flights and now displays like that:
-
-
After the reboot the first time Avionics Configurator had the same behavior… after a few minutes an a java update it is running ok now.
Still remains the 64bit exe problem.
-
So far what I found during testing. (Should I create a new thread for bug or similar issues?)
On Tornado IDS GER under fueselage most of bombs simply do not appear because rack / HP configs. Something does not work well. This is so strange because FF suffered from 100% same issue. The Tornado was imported without fixing this? With old rack.dat in my old MOD I fixed this but in BMS4 Tornado uses new bmsrack.dat. I can try to fix it. (Tornado IDS with '80s camo is one of my favorite jet.)
It is surprise to me that Patriot did not get the same launch method as SA-10.