Some 4.33 issues…

[Airbuster]

Ok, 4.33 is here and I’m really hyped. Already installed it and set most of the stuff. I just have trouble with the keyboard presets. I see there are new ones:

I used “keystrokes” preset in BMS 4.32. Which one of these new presets are similar to “keystrokes” or is there any way I can use the old preset?

Also I don’t have any cockpit shadows inside the new cockpits that came with 4.33 (Mig-29, F-18c etc.). How can I fix that?

Thanks in advance.

[Demo]

@Airbuster:

Ok, 4.33 is here and I’m really hyped. Already installed it and set most of the stuff. I just have trouble with the keyboard presets. I see there are new ones:

http://s28.postimg.org/nnlix9snh/2015_10_31_001431.png

I used “keystrokes” preset in BMS 4.32. Which one of these new presets are similar to “keystrokes” or is there any way I can use the old preset?

Also I don’t have any cockpit shadows inside the new cockpits that came with 4.33 (Mig-29, F-18c etc.). How can I fix that?

Thanks in advance.

You can copy over your key file from 4.32. But be advised a couple callbacks have been removed and others have been added that you can’t take advantage of with 4.33. I have been using the keystrokes key for months without issue.

To get up and flying and take it for a spin you can copy over your keystrokes key file (go to the 4.32 user folder and find keystrokes.key and load put in same place in 4.33 folder). But later it’s highly recommended you use the keyfiles that come with 4.33

[uri_ba]

I would avoid using old keystroke files as there were a lot of keyfile changes.

start with “Basic” see if that works of you,
and start adjusting it to your liking (under different name of course)

as for shadow, have you turned on multi-sampling and all the shaders?

[Airbuster]

uri_ba, here are my graphics settings, hope you can point out the issue:

I have selected “multisampling”, but I don’t see any additional options for it.

Also it seems that I don’t have any terrain shadows also.

@Demo, thanks. I’ll try with copying “keystrokes” for now since I’m too eager to fly, but later on I’ll have to create a new one for 4.33.

[uri_ba]

Seems to be on order.
64 bit or 32bit?

[molnibalage]

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.

[Airbuster]

64 bit. No biggie, all the F-16 pits are working fine and that’s what matters.

Thanks uri_ba

[Demo]

@molnibalage:

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.

The layout is for the default key file in 4.33. You can use your old key file that you’ve used before until you get sorted on the new key files.

Smile Monlibalage. Today is a good day :).

[molnibalage]

@Demo:

The layout is for the default key file in 4.33. You can use your old key file that you’ve used before until you get sorted on the new key files.

Smile Monlibalage. Today is a good day :).

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?

[Demo]

@molnibalage:

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?

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.

[Dee-Jay]

@molnibalage:

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.

[molnibalage]

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.

[Dee-Jay]

@Demo:

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?

[Demo]

@Dee-Jay:

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.

[Dee-Jay]

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

[Link_knight]

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.

[Dee-Jay]

@Link_knight:

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)

[Badger]

Just like in real only three indications off, closed, open

[dema]

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

[Kolbe-49th]

@Demo:

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