Jump to content

DDSSTT

Members
  • Posts

    347
  • Joined

  • Last visited

Posts posted by DDSSTT

  1. Unfortunately, no we cannot do that specifically with dynamic bort numbers. In the lua code for dynamic bort numbers, they are fixed to specific locations. The only way I know to have numbers that large and in those locations would be to have them as their own liveries, ex Blue Angel 1, Blue Angel 2,... 

    If you'd want it like that, I or someone else could make it for you - if its not already made...

  2. So I am running 4x BU036X, 2x BBI-64, 1x BBI-32, TRP, Winwing Throttle, Winwing Stick, 1x TM MFD, an extra keyboard dedicated to my F-18 pit, and a tablet for VRKneeboard. All of these are going through 2x 10 port USB HUBs. When my pit is not in use, the HUBs are un-plugged from my PC and the pit is stored out of the way of my desk.

     

    Every so often, like once a month, 1 or 2 of the Leo Bodnar boards will "loose" keybindings. What I see is, they have not so much as lost the bindings but the bindings are crossed between the boards, like my BU036X that is bound to my UFC will now be bound to my right back BU036X which controls cockpit lighting/INS/RDR/TPOD, etc.

     

    What I learned is all I have to do is just plug the USB HUBs and plug them back in, and the loss of my keybindings is fixed.

  3. I'm sorry, but "because its open beta" is not an excuse for ED to implement changes and then completely fail to implement said changes on their own product.

     

    This change should have stayed in an internal build until it was ready to push out in an OP patch, especially when its only half done and not even applied on the default skins.

  4. In the LUA description you have to remove all _001, _10, _100, _X001, _X100 bordnumbers.

    Then you have to add the lines :

     

    custom_args =

    {

     

    [1000] = 1.0,

    [1001] = 1.0,

    [1002] = 1.0,

    [1003] = 1.0,

    }

     

    Thanks, this fixes the tail, but the Nose, Intake, and Fuel Door are still messed up and still showing the background color.

     

    Seriously, why is ED making these changes and not even updating the stock skins? Why is it our job to figure this stuff out on our own?

  5. And we willingly accept that possibility and responsibility, but what we don't like is when the model itself breaks the skin. In this case, there is apparently no longer a way to have our custom bort texture applied, and even worse, there appears to be no alpha channel so any non-grey tail looks like garbage with no way to fix it.

     

     

    THIS ^

     

    Don't implement change for the sake of change. If you are going to change how bort numbers are displayed for the better, fine. BUT IT HAS TO WORK. In the current state is doesn't. This is doing nothing but causing issues that livery makers can't fix because its hard coded. This is just another example of ED changing/pushing something half-assed, not working, and unfinished.

     

    Same thing with the surprised change to the F/A-18C Helmets, nothing about it in the change log, and even default liveries are incorrect. In the military we have a term for this, the good idea fairy. Whats next, are they going to change the F/A-18C bort numbers too?

  6. I have been searching the webs for hours trying to find a single On-Off toggle switch where the toggle does not spin. Does anyone know where I can get one? I am using it for my launch bar for the F/A-18C.

  7. I've asked this question in a few different locations including discord, but never get any response.

     

    How do I create a multi-function keybinding when using a single Off-On Toggle Switch, that in the game has a switch cover on it?

     

    For example, the F-18 has a spin recovery on the right side that is a guarded toggle switch. When I switch the toggle switch ON, I would like to raise the cover and toggle the switch, and then when I toggle the switch to OFF, it toggles the switch down and closes the cover.

     

    I was able to get the key bindings to work with an (On)-Off-(On) switch, as seen in the below lua code, but I have been unable to figure out the script for a single on off switch.

     

    { down = ctrl_commands.SpinRecCover, up = ctrl_commands.SpinRec, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = 1.0, name = _('ALT Spin Recovery Switch Cover - OPEN'), category = {_('Instrument Panel')}},

     

    { down = ctrl_commands.SpinRec, up = ctrl_commands.SpinRecCover, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 0.0, value_up = 0.0, name = _('ALT Spin Recovery Switch - NORM'), category = {_('Instrument Panel')}},

×
×
  • Create New...