skypickle

SOLVED IT but I forgot to post the solution. The clickabledata.lua shows: -- Manual Advancement Button elements["RX_STEP_SW"] = mcabin_button( {0}, _("Cockpit.Mosquito.rockets_manual_button"), devices.ROCKETS, device_commands.Button_5, 384) So I added this line to the mosquito lua in the DCS-Exports folder in scripts in Saved games. [384] = "%.1f", The rocket selector button is a rotary button with range of 1 to 4 with increment by 1. The display is a momentary display button with DCS ID 384. Pushing the rocket selector button now works and the display in the cockpit advances properly showing the correct rocket. Only problem is the decimal. so I specify [384] = "%.0f", I suppose there is a nicer way to specify an integer. Now the only detail is when you spawn in, the streamdeck says 0 but the cockpit is showing 1 but once you start clicking the problem goes away. How do I get this change into the github?

Thank you so much. I enjoyed your L-39 Training Missions with English Voiceovers. I am trying to make a similar series for the F5E. My voice is horrible. What softwar did you use to make the dialog?

I thought i could look at how a good mission is structured. So I opened up the first mission from the a10 Iron Flag campaign . There were no triggers! How does that work?!

So I have a Total Controls Button Box. It works beautifully in all the modules I have. Yesterday I bought the L39 which was on sale. I bound up the basic controls as well as some of the NDB controls. However, all sounds from the communications menu were lost. I could not communicate with anyone from any of the entries nor could I hear replies. Obviously, when you select one of the entries (place chocks for example) it triggers a sound file. I narrowed the culprits down to two controls: RKL-41 Inner Beacon Frequency Tune Knob and RKL-41 Outer Beacon Frequency Tune Knob When these controls are bound to any axis on the Total Controls box, all audio from the communications menu is lost. Unbinding these controls restores communications. I also have two joysticks I built using an arduino micro as well as a TEENSY. The same phenomenon occurs with them. Binding any analog axis of any of these two devices (each device has 6 axes) to the above mentioned controls causes all sound to be lost from communications. Can anyone duplicate this? If I bind those two functions to buttons or encoders, the communications menu audio is not affected.

anyone ever make a F190 Dora profile?

@Raptor9I apppreciate your reply. I understand that there are many details interfering with detection of the laser-reflectivity of the target, atmospheric conditions, intervening interference,etc. But I am trying to simplify the mechanics of JTAC-aggressor teams. Does the combined slant range of designator and detector have an upper limit? Isnt there a 'procedure' with recommended altitudes/distances ?

So how far away can an f18 be to spot the laser designator from an apache? Obviously if apache is closer to the target, more energy is reflected since the intensity increases as the square of the distance to target decreases. But laser energy arriving at f18 decreases with square of slant range. These two compensating effects might cancel out suggesting a maximum length for apache slant range to target plus f18 slant range to target. (Assuming apache and f18 have similar detectors). What is this theoretical length? 9999m? So if apache is 3000 m to target then f18 munition has to acquire the reflected laser when it is 6999 m slant range away. I suppose the f18 could drop the munition blind from 30000 ft and hope for the best. But for f18 to detect the laser and show it in the cockpit, wouldnt it need to be closer than 6999 slant range if apache is 3000? Assuming a 45 degree slant, that means an altitude of about 5000 m. ? this neglects details like obscuration at ground level by dust and by clouds at altitude. And if apache is 5000 m away, f18 has to be 5000 away which at 45 deg is ~3500 m altitude - kind of low and at that altitude vulnerable to aaa and iglas. Might as well just go ccip or ccrp. anybody with real world experience please tell us standard target ranges for jtac and f18 when doing this kind of buddy lasing

I would be happy to collaborate with you. I have some experience with mission triggers and the subtle 'gotchas' that interfere with their execution. I have no knowledge of actual missions or CNATRA regs other than what I can read online so realism is not my forte. Rudel is however a far superior craftsman in this regard. Recently, I have been using Briefing Room to generate missions for me. https://github.com/akaAgar/briefing-room-for-dcs/releases/tag/beta-release-230118-1801 There is also this on the horizon: https://www.reddit.com/r/hoggit/comments/10hrmfk/the_all_new_dcs_web_editor_preview/?sort=new

I read LeCuvier's wonderful pdf and in section 5.10 he discusses how to create new axis commands. Although in section 5.11 he describes how to make buttons from axes, I cannot seem to figure out how to make an axis out of switch pairs. Specifically, for the HUD brightness in the A10C_2, HUD brightness is controlled by a rocker switch. clickabledata.lua has this entry elements["PNT-BTN-UFC-INTEN-RGT"] = default_button(_("Adjust HUD Brightness (Hold rocker)"), devices.UFC, device_commands.Button_28, 409 ) elements["PNT-BTN-UFC-INTEN-LFT"] = default_button(_("Adjust HUD Brightness (Hold rocker)"), devices.UFC, device_commands.Button_29, 409, -1, {-1.0, 0.0} ) devices.lua identifies the UFC as device 8 so I added this line to default.lua {action = 3028, cockpit_device_id = 8, name = _('HUD Brightness Knob')}, Unfortunately, this only makes the HUD fully bright when I twist the axis all the way to the right. Is there a better way to achieve this?

so tell me about how your stick felt (giggity)

Never flown a jet or helo IRL. Anyone here have firsthand experience in a real aircraft that is modeled in DCS? Specifically how damped does the stick feel? How much inertia is there? (Does the stick feel like you are waving a long stick?) how much of the plane’s vibration shows up as micro stick oscillation when hands off?

figured it out. Function - 0 on the UFC shows the info which can be toggled with button 10

go to the mouse column in control options and click the heading dropdown. choose load defaults.

I mapped the function appropriately and I can hear the click noise but the dial doesnt move. I've seen this before in some modules where the the physical click with the mouse has to be registered.

Why did you edit the lua file? Did you get the master mode selector to work?

I asked him if he would release the dora missions separately but they will only be part of his campaign for the Anton.

Thank you. That topic was actually started by me but I was never notiified of a reply. I also just saw it in the routine of checking my old threads.

Looking forward to this. BTW, any good campaigns for the Dora?

figured it out. radios need apu power.

I decided to go back to iron flag. I could hear biff in the first three missions (Nellis) but in the next set (navigation) I could not heat him. Yes I checked the kneeboard and used the fragged freqs.

how does one show ground speed or IAS in cdu?

yes but i dont know how to use it. It talks about IFF and I just set mode 3A digits to squawk. What are all the selections for?

is there a campaign like that of iron flag is for the A10? Something that teaches the F5 strengths in a simple way?

What does that dial just to the the left of the throttle do? Cant find it in the manual or chuck's

I guess a recent update 'streamlined' these control options. Presently, I can only assign buttons to increase and decrease these controls. Previously I had mapped axes to lights (aux,console,engine,flight,flood,form) and radio volumes (AIM seeker, ILS, TCN,FM,UHF,VHF) How I can I restore these axis controls? In the clickabledata.lua file I did find this section for example --Light System Control Panel elements["PTR-LGHTCP-POSITION"] = default_3_position_small_tumb(_("Position Lights, FLASH/OFF/STEADY"), devices.LIGHT_SYSTEM, device_commands.Button_8, 287) elements["PTR-LGHTCP-FORMATION"] = default_axis(_("Formation Lights"), devices.LIGHT_SYSTEM, device_commands.Button_9, 288, nil, nil, nil, nil, nil, {70, -135},{90,-45}) elements["PTR-LGHTCP-ANTICOLLISION"] = electrically_held_switch(_("Anticollision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_10, device_commands.Button_11, 289) elements["PTR-LGHTCP-ENG-INST"] = default_axis(_("Engine Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_1, 290, nil, nil, nil, nil, nil, {70, -135},{90,-45}) elements["PTR-LGHTCP-NOSE-ILLUM"] = default_2_position_small_tumb(_("Nose Illumination"), devices.LIGHT_SYSTEM, device_commands.Button_12, 291) elements["PTR-LGHTCP-FLIGHT-INST"] = default_axis(_("Flight Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_2, 292, nil, nil, nil, nil, nil, {70, -135},{180,-45}) elements["PTR-LGHTCP-AUX-INST"] = default_axis(_("Auxiliary Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_3, 293, nil, nil, nil, nil, nil, {70, -135},{140,-45}) elements["PTR-LGHTCP-SIGNAL-LTS"] = default_2_position_small_tumb(_("Signal Lights"), devices.LIGHT_SYSTEM, device_commands.Button_13, 294) elements["PTR-LGHTCP-ACCEL-COMP"] = default_2_position_small_tumb(_("Accelerometer & Compass Lights"), devices.LIGHT_SYSTEM,device_commands.Button_4, 295) elements["PTR-LGHTCP-FLOOD"] = default_axis(_("Flood Light"), devices.LIGHT_SYSTEM, device_commands.Button_5, 296, nil, nil, nil, nil, nil, {70, -135},{180,-55}) elements["PTR-LGHTCP-CONSOLE"] = default_axis(_("Console Light"), devices.LIGHT_SYSTEM, device_commands.Button_6, 297, nil, nil, nil, nil, nil, {70, -135},{180,-45}) elements["PTR-LIGHTS-LAND"] = default_3_position_tumb(_("Land Taxi Lights"), devices.LIGHT_SYSTEM, device_commands.Button_14, 655, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2) elements["PTR-ALCP-RSIL"] = default_axis(_("Refuel Status Indexer Lights"), devices.LIGHT_SYSTEM, device_commands.Button_15, 193, 0.0, nil, nil, nil, nil, {80, -45}) elements["PTR-ALCP-WPNSTA"] = default_axis(_("Weapon Station Lights. No function"), devices.LIGHT_SYSTEM, device_commands.Button_16, 195, 0.0, nil, nil, nil, nil, {90, -45}) -- No function in A-10C elements["PTR-ALCP-NVIS-LTS"] = default_3_position_tumb(_("Nightvision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_17, 194, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2) elements["PTR-FSCP-RCVR-LT"] = default_axis(_("Refueling Lighting Dial") ,devices.LIGHT_SYSTEM, device_commands.Button_18, 116, 0.0, nil, nil, nil, nil, {90, -45}) elements["PTR-ALCP-HARSSAS"] = default_2_position_tumb(_("HARS-SAS Override/NORM"), devices.AUTOPILOT,device_commands.Button_31, 196) elements["PTR-ALCP-FDBAL-TEST"] = default_button(_("Fire Detect Bleed Air Test"), devices.SYS_CONTROLLER, device_commands.Button_4, 198,1, {0,1}) It clearly indicates that the lighting controls have axes but they are not showing up in the new LARGE controls setting screen.