Some 4.33 issues…
-
I guess new keymap is exist because of new feautures. All new features can be used via cockpit clicking so new keymaps are not mandatory in case I wish to try new features?
Key map are needed for HOTAS (no hotspots for HOTAS in 3D pit) …
Personal keymap has to be rebuild using provided new basis. This effort, EVERBODY had to made it, even us. So now it is your turn.It is amazing … You seems the only one pissed off about that release!?! … if you want, you can stay in 4.32 you know!
Remember guys … Falcon4 is a study sim … And today we have to face another step. Even the older will have to go back to the books and will have some hard time before mastering like in 4.32. And I would even say that the harder will be for the oldest as old habits are difficult to be change.
-
I’m not pissed I simply felt myself lost. Without printing all docs I’m simply grounded. Regardless weeked is here I have to wait for learning next week when I can print materials.
I have to say I’m happy to see many of changes which are maybe based on my data supply thread.
-
No, some new features require the new callbacks. For example the harrier nozzles. But I was saying you can use your old key file to get up flying and try it out for yourself and then later take the time to recreate controller profiles, etc… With the new key files to take full advantage of what’s in 4.33.
Editing Old key file? … Insn’t that dangerous Demo? … or simplly more complex than resarting a personal set using the new ones?
-
Editing Old key file? … Insn’t that dangerous Demo? … or simplly more complex than resarting a personal set using the new ones?
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.
-
Oky. But as personal feedback: I had CTD’s back to Btest phases after Kolbe’s work on .key and coders callback “cleaning” by using my 4.32 keystrokes.key! I had to use proper 4.33 files to avoid crashes.
So this is why I am advising to avoid any other file than logbook.lbk
Thanks Demo … (And thank you for the hard work of those last days ) Congrats
-
I have noticed that the airbrake indicator does not rotate, its only shows closed when fully closed or fully open (lots of dots) even if they are only opened a little bit. (F16 block 50)
not sure if this is the place to post this. -
I have noticed that the airbrake indicator does not rotate, its only shows closed when fully closed or fully open (lots of dots) even if they are only opened a little bit. (F16 block 50)
not sure if this is the place to post this.Not a bug. It is on purpose. (Magnetic indicator)
-
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.