correct as is F-16 Parking brake not working since last update

[WHOGX5]

On 4/16/2024 at 1:49 PM, Exorcet said:

I know it's only a request right now, but would this be for all parked aircraft or would it be an option we can set on a per mission basis? I'd imagine in some cases you might not want the chocks in place (like QRA).

I mean, QRAs in real life always have chocks in place. It would probably take the average ground crew about 5 seconds to remove them, so it doesn't really affect how fast you can get off the ground. It does however stop the aircraft from rolling around without anyone in the cockpit.

[Exorcet]

On 5/14/2024 at 5:43 AM, WHOGX5 said:

I mean, QRAs in real life always have chocks in place. It would probably take the average ground crew about 5 seconds to remove them, so it doesn't really affect how fast you can get off the ground. It does however stop the aircraft from rolling around without anyone in the cockpit.

Fair, though in DCS the usual case is that someone is in the cockpit. The ground crew would also be a bit more proactive in reality, including being able to mention to the pilot if there is a problem (like forgetting the chocks) where as we need to fumble through the communications menu and depending on the mission might not even have a way to check the exterior state of the aircraft.

[Nezih]

On 3/21/2024 at 7:54 PM, void68 said:

Power is on, engine is running. Switching the Parking Break with the mouse works. Switching it with a keybind / external switch does not, ofc all other external switches work. The entry "AntiSkid-Switch, PARKINGBREAK" is a double entry and it's in orange, BTW like "MAIN POWER SWITCH (special) - MAIN POWER/BATT". Hovering over these commands tells me (in german, so a rough translation) "Different functions can't share the same name" .

 

So there are different functions behind the command entries - not by me.

There is no problem with the joystick assignments of the Parking Brake section. When it comes to assigning a key from the keyboard, only the "ANTI-SKID Switch - PARKING BRAKE" function does not work under any circumstances.

 

[rob10]

The fact that you have two entries for "ANTI-SKID Switch - PARKING BRAKE" and they are orange indicates you have some sort of problem in your bindings file and is why it isn't working for you.  Do a search because I've seen the issue before but I can't remember all the details.  You may need to re-create your F-16 bindings file.

[Nezih]

6 hours ago, rob10 said:

The fact that you have two entries for "ANTI-SKID Switch - PARKING BRAKE" and they are orange indicates you have some sort of problem in your bindings file and is why it isn't working for you.  Do a search because I've seen the issue before but I can't remember all the details.  You may need to re-create your F-16 bindings file.

Can someone who thinks they have no problems with this issue please upload the "default.lua" file at the address below?

...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard

[Maverick806]

Deleting the file and running a repair should redownload that file for you. 

https://www.digitalcombatsimulator.com/en/support/faq/repair/

[LeCuvier]

18 hours ago, Nezih said:

Can someone who thinks they have no problems with this issue please upload the "default.lua" file at the address below?

...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard

I would rather suggest that you post your two "default.lua" files under
"...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard" and
"...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" respectively.
I would then be able to see which of the two files causes the problem.

[Nezih]

13 hours ago, LeCuvier said:

I would rather suggest that you post your two "default.lua" files under
"...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard" and
"...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" respectively.
I would then be able to see which of the two files causes the problem.

Thank you Lecuvier. 

I share the relevant files by renaming them.

default - Joystick.lua default - Keyboard.lua

[void68]

Isn't that exactly the problem as I described it and there is NO solution but has to be corrected by the devs? At least in german localization?

 

Just to clarify so that this thread / problem doesn't vanish even if Nezih gets his problem fixed. It's still an issue the update cycle created 2,5 turns before and what has been working prior. I still wait desperately for the promised fix for 1,5 updates!

[LeCuvier]

@Nezih: I compared your files with mine. Results:
Your "joystick" file is exactly the same as mine.
Your "keyboard" file differs in 3 lines. The first 2 are added lines for the ejection seat safety lever bindings. They should be o.k., I suppose you added these?
The 3rd one has an altered line for the parking brake which is apparently causing the issue. Here is your line:

{down = gear_commands.AntiSkidSw_EXT,	up = gear_commands.AntiSkidSw_EXT,	cockpit_device_id = devices.GEAR_INTERFACE,		value_down =  1.0,	value_up = 0.0,	name = _('ANTI-SKID Switch - PARKING BRAKE'),		category = {_('Left Auxiliary Console')}},

Here is my corresponding line:

{down = gear_commands.ParkingSw_EXT,		up = gear_commands.ParkingSw_EXT,	cockpit_device_id = devices.GEAR_INTERFACE,		value_down =  1.0,	value_up = 0.0,	name = _('ANTI-SKID Switch - PARKING BRAKE'),		category = {_('Left Auxiliary Console')}},

I removed the huge space in the beginning of both lines to make them more readable.
I attach the "repaired" keyboard file.


 

default - Keyboard.lua

Edited May 21, 2024 by LeCuvier

[LeCuvier]

4 hours ago, void68 said:

Isn't that exactly the problem as I described it and there is NO solution but has to be corrected by the devs? At least in german localization?

 

Just to clarify so that this thread / problem doesn't vanish even if Nezih gets his problem fixed. It's still an issue the update cycle created 2,5 turns before and what has been working prior. I still wait desperately for the promised fix for 1,5 updates!

It certainly looks the same at the surface. You are using a "germanized" version, and so I cannot use the "compare" function in NotePad++. But I can take a look the hard way.
If you post your two "default.lua" I will look at them.

[Nezih]

5 hours ago, LeCuvier said:

@Nezih: I compared your files with mine. Results:
Your "joystick" file is exactly the same as mine.
Your "keyboard" file differs in 3 lines. The first 2 are added lines for the ejection seat safety lever bindings. They should be o.k., I suppose you added these?
The 3rd one has an altered line for the parking brake which is apparently causing the issue. Here is your line:

{down = gear_commands.AntiSkidSw_EXT,	up = gear_commands.AntiSkidSw_EXT,	cockpit_device_id = devices.GEAR_INTERFACE,		value_down =  1.0,	value_up = 0.0,	name = _('ANTI-SKID Switch - PARKING BRAKE'),		category = {_('Left Auxiliary Console')}},

Here is my corresponding line:

{down = gear_commands.ParkingSw_EXT,		up = gear_commands.ParkingSw_EXT,	cockpit_device_id = devices.GEAR_INTERFACE,		value_down =  1.0,	value_up = 0.0,	name = _('ANTI-SKID Switch - PARKING BRAKE'),		category = {_('Left Auxiliary Console')}},

I removed the huge space in the beginning of both lines to make them more readable.
I attach the "repaired" keyboard file.


 

default - Keyboard.lua 181.74 kB · 0 downloads

 

@LeCuvier you are right. I added for two controls (Seat Lever and Smoke Device)

There are no longer any incorrect lines in the key file. (orange coloured). Below I present the picture and operation of your new Keyboard file. Thank you very much for this great work.

 

[void68]

Am 21.5.2024 um 16:47 schrieb LeCuvier:

It certainly looks the same at the surface. You are using a "germanized" version, and so I cannot use the "compare" function in NotePad++. But I can take a look the hard way.
If you post your two "default.lua" I will look at them.

That would be more than I can ask for...  I uploaded both the joystick and keyboard .luas.
default.lua

default.lua

[LeCuvier]

@void68: I have looked at your two files. Findings:

1. I expected to look at "germanized" versions of "default.lua", but they are not. So apparently the localization is defined in a separate file.

2. Your keyboard file is the same as mine.

3. Your joystick file is very different. You (or someone else) have made additions to it, which probably do not cause your issue. But you are also missing a good number of lines which have probably been added to the stock files after you made the additions. It seems that you are using an older version of the file with your additions. Not good.
There is also an invalid binding in the category "Special for joystick". My flie has this line:

{down = gear_commands.ParkingSw_SPEC, up = gear_commands.ParkingSw_SPEC, cockpit_device_id = devices.GEAR_INTERFACE, value_down =  1.0,	value_up = 0.0,	name = _('ANTI-SKID Switch (special) - PARKING BRAKE/ANTI-SKID'), category = {_('Special For Joystick'), _('Left Auxiliary Console')}},

In your file, this line shows:

Quote

{ down = gear_commands.AntiSkidSw, up = gear_commands.AntiSkidSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down =  1.0, value_up = 0.0, name = _('ANTI-SKID Switch (special) - PARKING BRAKE/ANTI-SKID'), category = {_('Special For Joystick'), _('Left Auxiliary Console')}},

 

Padding removed in both to facilitate reading. Both lines have the same name "ANTI-SKID Switch (special) - PARKING BRAKE/ANTI-SKID", but in your file they have the wrong command ID, which overlaps with a command in the other Anti-Sid switch bindings. While this seems related I cannot tell with certainty that this is causing your problem, but you could try what happens if you correct your line. At any rate, this violates the rule that you cannot have two different command definitions sharing the same name.

Conclusion:
The issue I noted under 3. is certainly suspicious but I'm not sure it causes your problem. The situation of an outdated file with additions and an invalid line of code makes it difficult to understand what's going on. While I cannot rule out that the issue comes from localization, that would not my primary suspect.

Recommendations:

1. Take your additions out of the "default.lua" in the game folder and use them with the "Command Injector" by @Quaggles. There, the additions will be in a "default.lua" under "Saved Games", and you can let DCS World update all your game files.

2. As a first step, make a backup copy of your "default.lua" under "joystick" and let DCS World run a repair. Then check if your binding work fine.

3. If you don't want to go to the Command Injector, copy all your added lines into a holding file. Then, after a successful repair (or update), copy them "en bloc" into your "default.lua". This will make it easier to restore your additions after an update.

[void68]

Am 30.5.2024 um 16:55 schrieb LeCuvier:

@void68: I have looked at your two files. Findings:

3. Your joystick file is very different. You (or someone else) have made additions to it, which probably do not cause your issue. But you are also missing a good number of lines which have probably been added to the stock files after you made the additions. It seems that you are using an older version of the file with your additions. Not good.

3.) yes, after each update I moved the backup joystick file back to the original location. I understand I overwrote updates in the stock joystick.lua. So I will have to edit my modified lines into the stock.

I will edit the stock lua with the new settings and report back.

edit: you nailed it. Works now. Why the Anti-Skid Parking Brake got a totally different subsumption is incomprehensible for me..

 

A big "thank you"!

 

Edited June 3, 2024 by void68

[LeCuvier]

4 hours ago, void68 said:

A big "thank you"!

gern geschehen!