Jump to content

Recommended Posts

Posted

Hi, I have a little question to ask you. Given that I have searched a bit everywhere but I have not found the answer I am looking for.
I would like to know if it is possible to know what a panel device id corresponds to.

For example:

Panel Device id: 17

I tried searching the various lua files, but it's a jungle, and I couldn't find anything I need.
Thanks everyone for the help

Posted
4 hours ago, Facocero said:

I would like to know if it is possible to know what a panel device id corresponds to.

For example:

Panel Device id: 17

 

Yes, it is possible. You don't know which aircraft are you using, the next example is for the A-10C II, but all others are similar. The LUA file is called devices.lua, and it's located on the \cockpit\scripts\ folder:

 

xy6Ztyv.jpg

 

Inside the file is a list of devices ... the first one is device 1, the second is device 2, etc., like this:

 

nSqJb0C.jpg

 

 

 

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)
8 hours ago, Rudel_chw said:

 

Yes, it is possible. You don't know which aircraft are you using, the next example is for the A-10C II, but all others are similar. The LUA file is called devices.lua, and it's located on the \cockpit\scripts\ folder:

...............................................................

Thanks for the reply.
Yes, I had seen that file, but I was not convinced that it could be useful. I'll give you an example to make me understand.
I'm using the UH-1H, according to that file, the device Id: 17, corresponds to IFF, but I don't need much because I have not found anything with that match, or at least I have not found it.
Basically, I'm trying to learn and understand why I can open the gunner door, but I can't close it.
I saw a mission that I unloaded, and the hatches open and close properly, and I wanted to understand why it doesn't work for me. I went to see that mission in the editor and saw that in addition to having Clickable Execution on the panel Id: 9 command: 3036
val: 1, also has
Id: 17 command: 3018
Val: 1 and
Id: 17 command: 3013
val: 1
I wanted to understand why the other two commands, but as I said I can't find it anywhere.
Thanks again

ah I add that to find the ids in the command settings, I enabled the misison editor tooltip, so as to immediately see the ID of each command

Edited by Facocero
Posted
3 hours ago, Facocero said:

...
I'm using the UH-1H

...
ah I add that to find the ids in the command settings, I enabled the misison editor tooltip, so as to immediately see the ID of each command

 

 

On my UH-1 I have different commands, maybe you are seeing the UH-1H in game mode or gunner mode?

 

Open/Close both front doors: X:SET COMMAND(71)

Open/Close Left Gunner Door: X:COCKPIT PERFORM CLICKABLE ACTION(9, 3036)

Open/Close Right Gunner Door: X:COCKPIT PERFORM CLICKABLE ACTION(9, 3035)

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
57 minutes ago, Rudel_chw said:

 

On my UH-1 I have different commands, maybe you are seeing the UH-1H in game mode or gunner mode?

 

Open/Close both front doors: X:SET COMMAND(71)

Open/Close Left Gunner Door: X:COCKPIT PERFORM CLICKABLE ACTION(9, 3036)

Open/Close Right Gunner Door: X:COCKPIT PERFORM CLICKABLE ACTION(9, 3035)

I don't know what you mean by game mode, gunner etc.
I am at the controls of the UH-1h and I wanted, once landed, to open the rear hatch of the gunner. I succeed, with the X:COCKPIT PERFORM CLICKABLE ACTION(9, 3035, 1)command
but I can't close it. So I went to see about a mission, in which opening and closing works regularly, and I saw, as already mentioned, that in addition to the command to open your door, there is this X:COCKPIT PERFORM CLICKABLE ACTION(17, 3018, 1)X:COCKPIT PERFORM CLICKABLE ACTION(17, 3013, 1)

Without these two commands the door will not close. And I wanted to understand what they do.

Posted (edited)
52 minutes ago, Facocero said:

I don't know what you mean by game mode, gunner etc.

 

The UH-1H has several different Set of Controls that you can bind at Options -> Controls, I usually use the UH-1 Sim Mode, so I was wondering if you maybe were using commands from the other Modes.

 

52 minutes ago, Facocero said:

I am at the controls of the UH-1h and I wanted, once landed, to open the rear hatch of the gunner. I succeed, with the X:COCKPIT PERFORM CLICKABLE ACTION(9, 3035, 1)command
but I can't close it. So I went to see about a mission, in which opening and closing works regularly, and I saw, as already mentioned, that in addition to the command to open your door, there is this X:COCKPIT PERFORM CLICKABLE ACTION(17, 3018, 1)X:COCKPIT PERFORM CLICKABLE ACTION(17, 3013, 1)

Without these two commands the door will not close. And I wanted to understand what they do.

 

I don't know what they do .. to close the Doors I just use these commands:

 

Open/Close both front doors: X:SET COMMAND(71)

Open/Close Left Gunner Door: X:COCKPIT PERFORM CLICKABLE ACTION(9, 3036)

Open/Close Right Gunner Door: X:COCKPIT PERFORM CLICKABLE ACTION(9, 3035)

 

The same command opens or closes the door. Here is a sample mission (since the Huey always spawns with the front doors open, on the first trigger I just close them), the 2nd trigger opens all doors, then the third trigger closes all of them again.

 

UH-1H - Test Door triggers (by Rudel_chw).miz

Edited by Rudel_chw

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted

Thanks, I will definitely try the attached mission.
However, I do the exact same thing, for the right rear door, but then I can't close it. Boh

Posted (edited)

I tried your mission, and the gunner's doors actually open.

But I do the exact same thing, except waiting for the response from the user.
To understand, only X:COCKPIT PERFORM CLICKABLE ACTION(9, 3035, 1) and X:COCKPIT PERFORM CLICKABLE ACTION(9, 3036, 1) but as I said, they open, but then they don't close.

I got a doubt and I did an experiment. Since with X:COCKPIT PERFORM CLICKABLE ACTION(17, 3018, 1) and X:COCKPIT PERFORM CLICKABLE ACTION(17, 3013, 1) which apparently no one knows what they are, I replaced 17 with an invented number 255, and it works. So (if I'm wrong, forgive me), it could be a small bug.

Edited by Facocero
Posted
19 minutes ago, Facocero said:

I tried your mission, and the gunner's doors actually open.

But I do the exact same thing, except waiting for the response from the user.

 

 

The response is there just so that you may command when to open and when to close. I don't believe there is a bug, since this works on my mission, and starting to use invented parameters is not a time-effective way to learn this .. basically the cockpit perform clickable action is just mimicking the clicking you do with the mouse, it should work correctly, and on my sample mission it does, so ... no Bug 🙂

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)

 

6 minutes ago, Rudel_chw said:

 

The response is there just so that you may command when to open and when to close. I don't believe there is a bug, since this works on my mission, and starting to use invented parameters is not a time-effective way to learn this .. basically the cockpit perform clickable action is just mimicking the clicking you do with the mouse, it should work correctly, and on my sample mission it does, so ... no Bug 🙂

So can you explain to me why you don't close the hatch to me?
And why the mission I did, there are two commands that apparently do not exist id: 17 or rather exists as a device, but I do not find any correspondence in the command settings?
And why as soon as I entered a valid id, in addition to the correct one to close the hatch, now it works?
In my opinion it is clear that there is something wrong. 🙂

Edited by Facocero
Posted

I tried to recreate a very short mission, and it seems to work with just the command to open and close.
I don't understand why the mission I was preparing doesn't work. I will try to investigate better.

Posted
57 minutes ago, Facocero said:

In my opinion it is clear that there is something wrong. 🙂

 


ok, sorry I wasn’t able to really help you with this, feel a bit like I wasted my time 😞

  • Thanks 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
6 minuti fa, Rudel_chw ha scritto:


ok, sorry I wasn’t able to really help you with this, feel a bit like I wasted my time 😞

Instead you helped me a lot and I thank you.
Unfortunately, not speaking English correctly, I had a hard time making myself understood.
Anyway, I did more tests, and I managed to get the mission to work with a single command to both open and close the hatch. I was misled, the fact that it wasn't working and then I went to see a mission that I was sure was working and I had seen that command which is useless.
Thank you very much, you have been very kind

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...