Jump to content

Red Dog

Members
  • Posts

    109
  • Joined

  • Last visited

2 Followers

About Red Dog

  • Birthday 03/24/1972

Personal Information

  • Flight Simulators
    Falcon BMS, X-plane, DCS
  • Location
    Brussels
  • Interests
    Anything that flies
  • Occupation
    Q&A
  • Website
    http://www.combatsimchecklist.net/

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Next one: embedded checklists in the CPD with the DCS kneeboard
  2. Here's the first of I hope many series of Vlogs using the pit: MP Air to air refuel in the persian gulf
  3. The F-16 cockpit was started in 2004 and built for Falcon 4.0. It flew BMS for 15 years. Since 2021 I switched to DCS and today I am ready to restart publishing Vlogs flying the pit. The pit flies both sim without reprograming, so all key inputs are common between DCS and BMS, it took a while to setup. The software interface is also common thanks to a little software gem called DCStoF4 allowing to put life in the DCS cockpit by reading the BMS shared memory. This may sounds strange to most of you but when all the cockpit has been interfaced to read the BMS shared memory, it's much easier to keep doing it rather than reprogramming the multiple third party apps that are necessary to interface the pit. The small caveat of course is that the BMS shared mem needs to be active when I run DCS. Small price to pay to have a pit flying two totally different sim. Full report of the WIP build is on Viperpit Enough talk, Here's an introduction picture of the pit and I will use this topic to post Vlogs of solo and MP flights with the F-16 in DCS
  4. Sec checks are still impossible to perform at ramp due to the above. so kind bump for this issue hoping to see it solved one day
  5. bumped into this issue as well the FUEL QTY TEST keybind seems to emulate the FUEL QTY NORM position however they may have different keypress declared in the controls. It works fine in the UI - control options. Moving the rotary switch to TEST shows test and moving it back to NORM shows the keybind for NORM. All other position works equally fine But in 3D it is different QTY TEST cannot be emulated, rotary remains to NORM NORM works as all other positions (RSVR, INT WING, EXT WING, EXT CENTER) - using the declared keystroke for QTY NORM moves the switch back to NORM => OK - using the declared keystroke for QTY TEST moves the switch back to NORM => not OK It is easily checked by placing the rotary to INT RES (any position except NORM) for instance and using the keyboard to type the keystroke for TEST => knob goes back to NORM Thanks LeCuvier for your work around, I'll implement it right away.
  6. Hello gents is there a way to have more radio menu shortcuts a la A/A refueling - "Ready for precontact" radio call @LeCuvier ? This one above is really helpful to avoid having to mess with the radio menu options close to the tanker. Alternatively, is there a way to declare more custom ones line the one above for instance: A/A refueling - "Intent to rejoin" radio call Ground crew - "Place chocks" radio call Ground crew - "Remove chocks" radio call (the last two not being so critical since we're on the ground and could navigate the menu - but IMHO at least the request join up with tanker would be useful. Many thanks as always
  7. Just want to confirm this issue. At night when you dim down the in game MFDS (F-16 in my case) to a non bright level, the exported MFDS are completely invisible It would be great if both in game and exported have the same BRT levels Hopefully that gets sorted one day.
  8. another vote for this to be enhanced a bit. I feel the left one UP and Down is OK but the right one Forward and Backward is a real pain to see both during daylight and night AAR The issue I feel is not really brightness but lack of contrast due to a white line of lights against the green reference light. That is what makes it very hard to see IMHO just removing that white line would tremendously help In the above picture I know I'm great on up and down but I have no way to know where I am front/aft from the light only
  9. yep, first thing is to ensure you have admin rights with notepad++ then from my understanding (Lecuvier will correct me if I'm wrong) then you can either do it in keyboard\default.lua or joystick\default.lua depending if you want to assign this to a keyboard keypress (then do it in keyboard\default.lua) or a DX button of one of your button boxes or joysticks - then do it in joystick\default.lua I did it in joystick\default.lua and assigned it as a DX button of one of my BU0836
  10. in my case as soon as I declare the RWR in my multi screen lua file, following the above procedure, my multi screen lua files gets deleted from the list of LUA files DCS sees from the UI .Just like I reported there: If I remove my lines for exporting "RWR" from the multiscreen lua files, then at next boot DCS sees my multi screen lua file again but as soon as I declare RWR I'm toast I feel DCS really does not want you to export it honestly though I dropped trying exporting the RWR when I fought that issue a few days ago. I tried this morning again following this topic procedure and I hit the exact same issue again. Don't know why it seems to work for some but not for me in any way
  11. You're right, I found them - even better Silly me then, I must have missed them the first time To my defense Pitch trim knob really doesn't make me think of the ADI, but rather the MAN TRIM pitch controls (which are not in the instrument section) My apologies. and thank you
  12. Could I abuse and ask the same for the ADI adjust symbol? (the small airplane model used to set right in the center of the ADI) It's currently implemented as a potentiometer, but not as a key as far as I can see. Probably not something widely used, but in a pit with the seat adjust and flying IFR, it is useful Thanks I tried this: { down = alt_commands.ADI_ZeroPitchTrimLeft, up = alt_commands.ADI_ZeroPitchTrimLeft, value_down = -1.0, value_up = 0.0, cockpit_device_id = devices.ADI, name = _('ADI Trim Knob - CCW'), category = {_('Instrument Panel')}}, { down = alt_commands.ADI_ZeroPitchTrimRight, up = alt_commands.ADI_ZeroPitchTrimRight, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ADI, name = _('ADI Trim Knob - CW'), category = {_('Instrument Panel')}}, and although I see the lines in the control binding screen, assigning it and testing it does not give any result. The default potentiometer assignation works though
  13. I'd rather wish for ED to look up this problem and let us move both the kneeboard and the control indicator as we users would see fit without breaking the IC? I'm sure it's not on purpose that it breaks the IC, it's just an omission because the kneeboard and the stick indicator (and maybe others) have not been taken into the multi monitor big picture (pun intended) Maybe the right way to fix this is to let us manage these two with dedicated common viewports. Problem solved. - No more weird default position which change from one user to another - Users gets flexibility and can place their stuff where they want it - No IC failure - everybody happy and sorry for the added work for the devs. So Ed, pelase report this issue and see if this can be fixed - Thanks In the meantime, we'll have to find or own way till this is addressed eventually.
×
×
  • Create New...