[Briefing Images]

39 minutes ago, dark_wood said:

Maybe they are larger than 1024x1024?

This guy doesn't show either.

[Briefing Images]

Hey all. I am trying to load in some briefing images but nothing shows up in the directory to load from. All the images are PNG.

The images are in the folder I am trying to load from but the folder is empty when I use the tool in the mission editor to load them.

 

Any ideas?

[New to VR]

Hey all,

I am trying to decide between the Quest 2 and the Rift S. Everyone I have talked to about buying a headset says to get the best resolution you can afford for DCS. Everyone is telling me to get the Q2 but isn't the Rift S better in resolution? 

Specs from Oculus website:

Quest 2 resolution: 1832x1920 Per eye

Rift S resolution: 2560x1440

 

What am I missing?

 

[F16 Auto Lase After Bomb Release?]

1 hour ago, bart said:

What about the IRL aircraft, did that have an auto lase feature?

Good question. I read on another forum that you could set the time the laser would turn on on the lase portion of the DED but I couldn’t find it. If it’s not done in the actual viper then it shouldn’t be in the game. However, I thought this was a feature of the pod itself, maybe I’m wrong.

[F16 Auto Lase After Bomb Release?]

Hey all,

 

Is it possible to auto lase on the F16?

 

 

 

 

[A-G Stores Page won't come back]

This issue isn’t resolved. I was in A-G last night and needed to power on the HARMs. I went to the SMS page and it listed all my stores. The INV button was missing and I couldn’t get the HARMs powered on. Had to reload the F16

[Maverick Alignment]

On 9/25/2021 at 10:03 AM, Chaos_Out said:

Also, as long as you don't Jettison the rack, you can rearm mavs and shouldn't need to align again.

Whoa, I didn’t think about this… most excellent! Now if I can just stop getting shot down…

[Maverick Alignment]

14 hours ago, Dannyvandelft said:

You did it right. Do NOT do TMS aft after clicking boresight on the WPN screen. Just cycle to the next missile. Here's how I do it, and it works perfectly.

TGP on
WPN on
Slave TGP to target
MAN to AUTO
TMS up
Make WPN page SOI
slave Maverick 1 to target
TMS up
Push NWS button to select Maverick 2
Slave Maverick 2 to target
TMS up
Push NWS button to select Maverick 3
And so on.

Once you cycle back to Maverick 1, it will be off target again but once you lock a target in flight, it'll work. Just make sure you're in range or the handoff won't complete.

Sent from my SM-G960U using Tapatalk
 

Thanks!

 

Question: I thought you only had to align twice. If you have 3xDs on each wing then you would only need to align the weapon station. 

[Maverick Alignment]

8 hours ago, Ignition said:

 

Yes, at least in DCS if you TMS down after boresight the maverick will look off but it will work, it happened to me several times. Don't forget to boresight both pylons.

Yep, realized this a few mins ago. Odd that it does this, should just recenter. I also noticed that sometimes I have to TMS aft with the Maverick SOI after auto handoff from TGP. The handoff makes it to a T for the selected Maverick. I have to TMS aft on the Maverick SOI and then TMS forward to make the shot. The Maverick crosshairs as where they should be but I can’t get it to auto handoff to a C after firing from a successful auto handoff. 
 

hope that makes sense

8 hours ago, Viciam1 said:

Did you set the hand off to Auto on the TGP screen from Man?

I have done it both ways. 

[Maverick Alignment]

Hey all,

 

I am trying to align the Mavericks but it doesn't work.

 

I am on the ground with a tank located on the other side of the runway. I have the F16 pointed at the tank and I am positioned at the opposite end of the runway. I set the Mavericks to PRE mode. I slew the TGP to the tank and TMS forward to lock the tank. I then slew the Maverick (which is not pointed towards the tank, it's off) and center it on the tank then TMS up. The Maverick locks the tank and BSGT appears and I click it. That should be it right?

 

If I TMS aft on the Maverick to unlock the target, the Maverick slews back to being off again.

 

Anyone have any luck with this? I have watch Wags video on aligning the Mavs but I can't get it to work.

[Radar elevation sensitivity]

9 hours ago, LeCuvier said:

It does not matter at all, as long as you put them into the right block of lines. Personally, I put all added lines at the end of the block for key commands., like this:
 

--added HWF
{down = mmc_commands.Alt, up = mmc_commands.Alt, cockpit_device_id = devices.MMC, value_down =  1.0, value_up =  0.0, name = _('HUD Altitude Switch 2-POS RADAR/BARO'), category = {_('Right Console'), _('HUD Control Panel')}},
{pressed = hotas_commands.THROTTLE_ANT_ELEV_UP, cockpit_device_id = devices.HOTAS,    value_pressed =  0.2, name = _('ANT ELEV Knob - CW Fine'), category = {_('Throttle Grip'), _('HOTAS')}},
{pressed = hotas_commands.THROTTLE_ANT_ELEV_DOWN, cockpit_device_id = devices.HOTAS,    value_pressed = -0.2, name = _('ANT ELEV Knob - CCW Fine'), category = {_('Throttle Grip'), _('HOTAS')}},
{down = iCommandPlaneGearUp, up  = iCommandPlaneGearDown, name = _('LG Handle 2-Pos UP/DOWN'), category = {_('Left Auxiliary Console')}},
{down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down =  1.0, value_up = -1.0,    name = _('Autopilot PITCH Switch ALT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}},
{down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0,    value_up = -1.0, name = _('Autopilot PITCH Switch ATT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}},
{down = fcr_commands.PwrSw, up = fcr_commands.PwrSw, cockpit_device_id = devices.FCR, value_down =  1.0, value_up =  0.0,    name = _('FCR Switch 2-Pos FCR/OFF OFF'), category = {_('Right Console'), _('SNSR PWR Control Panel')}},
{down = ufc_commands.FLIR_GAIN_Sw, up = ufc_commands.FLIR_GAIN_Sw, cockpit_device_id = devices.UFC,    value_down =  1.0, value_up =  0.0, name = _('ICP FLIR GAIN/LEVEL 3-Pos Switch GAIN/LVL'), category = {_('Instrument Panel'), _('ICP')}},
{down = ufc_commands.FLIR_GAIN_Sw, up = ufc_commands.FLIR_GAIN_Sw, cockpit_device_id = devices.UFC,    value_down =  -1.0, value_up =  0.0, name = _('ICP FLIR GAIN/LEVEL 3-Pos Switch AUTO/LVL'), category = {_('Instrument Panel'), _('ICP')}},
{down = rwr_commands.Power, up = rwr_commands.Power, cockpit_device_id = devices.RWR, value_down =  1.0, value_up =  0.0, name = _('RWR Indicator Control POWER Button 2-Pos DEPR/REL'), category = {_('Left Auxiliary Console'), _('THREAT WARNING AUX Panel')}},
{down = cpt_commands.EjectionSafetyLever, up = cpt_commands.EjectionSafetyLever, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever 2-Pos ARMED/LOCKED'), category = {_('Systems')}},
{down = cpt_commands.EjectionSafetyLever, value_down = 1.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever ARMED'), category = {_('Systems')}},
{down = cpt_commands.EjectionSafetyLever, value_down = 0.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever LOCKED'), category = {_('Systems')}},

})

 

Fixed and works!

 

Thanks for all your help! Not sure what the other lines of script to (still new to the F16). Not sure if I need them ore not.

[System Target While in TWS is Solid White]

47 minutes ago, BIGNEWY said:

Hi, 

 

this is heavily work in progress at the moment and will be changing as we progress. 

 

thank you

 

Bignewy, 

 

Thanks for the response. I assume this is a known issue. Can still fly the 16 so no worries! Great module even in it's current state. 

 

You guys brought simulators to a whole other level.

 

Thanks

[System Target While in TWS is Solid White]

Hey guys!

 

I searched but didn't find anything on the above. Maybe I am doing something wrong.

 

I have been reading Chuck's Guide on the F16 with regards to the Track While Scan (TWS) radar mode. I setup three MIG29s flying towards me about 35nm from my F16 co-altitude in the mission editor and ran it. I set the radar to TWS and I can see the search targets when the radar does its first sweep and by the 2nd sweep they turn into track targets. Following Chuck's guide, I set the radar cursor over a track target and TMS up which should cause the track target to transition to a system target. However, there is no change in symbology, nothing happens. If I TMS up again then the track target turns into a bugged target (circle around a solid white square). If, however, I TMS up (ONCE) on all 3 track targets (symbology still shows track target for all 3 after I do this) I am then able to cycle between the "indicated" track targets with TMS right turning them (one at a time) into a bugged target (again, circle around a solid white square). I can ripple 3x120s and bring them down. 

 

I hope this makes sense. Anyone else have this issue? I attached an image.

 

Thanks for the help!

[Radar elevation sensitivity]

1 hour ago, LeCuvier said:

That might be a good idea.

Ok will do. Just to confirm, I copy and paste your two lines right underneath the two original lines right? Not up elevation under up elevation, right?

[Radar elevation sensitivity]

19 hours ago, LeCuvier said:

I do not have the 4 lines displayed in orange, because my added lines have " Fine" added to the names of the added bindings.

I suspect you added the new lines with the same names as the original lines. In other words, you have lines with identical names but different code. That's an (non-lethal) error condition.

I could have changed the original lines as you did, but I wanted to keep the original lines for quick coarse adjustments.

So should I return the old lines back to original and copy and paste your lines right under them?

[Radar elevation sensitivity]

8 hours ago, LeCuvier said:

@LowlyslowsYou copy the two lines above and paste them into the "default.lua", using the free Notepad++ editor. It's important you paste them into the right block of code. Refer to the document for specifics.

 

Surprisingly, I got it to work! However, it might be the wrong thing. I just searched for the code: THROTTLE_ANT_ELEV_UP and changed both UP/DOWN to 0.1/-0.1. When I went back into DCS I noticed a second set of antenna elevation binds (4 total and now orange in color). I bound to the new set and now the sensitive is perfect. 

 

Thoughts? I know this isn't what you recommended but it worked plus I didn't see your response until just now!

 

Thanks for the help!

[Radar elevation sensitivity]

2 hours ago, LeCuvier said:

The how-to document and additions for several aircrafts are in this thread:

https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#elControls_4646929_menu

 

WOW.. You put a ton of time into this. Thank you!

 

I can barely use email so this is gonna be interesting!! I read your instructions but it's not clicking for me.. Not sure if I need to just copy and past the script above in or if I need to modify what's in there. 

 

 

 

[Radar elevation sensitivity]

On 4/3/2020 at 5:40 AM, LeCuvier said:

As I'm not a patient guy, I have fixed it for myself by adding these 2 lines to the "default.lua":

{pressed = hotas_commands.THROTTLE_ANT_ELEV_UP, cockpit_device_id = devices.HOTAS,    value_pressed =  0.2, name = _('ANT ELEV Knob - CW Fine'), category = {_('Throttle Grip'), _('HOTAS')}},
{pressed = hotas_commands.THROTTLE_ANT_ELEV_DOWN, cockpit_device_id = devices.HOTAS,    value_pressed = -0.2, name = _('ANT ELEV Knob - CCW Fine'), category = {_('Throttle Grip'), _('HOTAS')}},

 

The values after "value_pressed" determine the sensitivity of the command (higher number --> faster, smaller number --> slower).

 

Hello, can you provide some more detail on how to use your code to solve the issue please? Like a "how to" place the code in the file? What software do I need to do it?

 

Thanks in advance. I just got the F16 module and I am using my rotary encoder dial on my VIRPIL CM3 and the radar jumps altitude blocks. 

[Radar elevation way too sensitive on button]

Just purchased the F16, this issue still is ongoing? I am using the VIRPIL CM3 throttle and a dial for the thumb is there just for this purpose (IMO). I even tried an axis and the jump in altitude blocks is huge..

 

Anyone have an idea?

[Radar elevation]

Any update on this? I just started flying the 16 and this is very bothersome. I’m using a Virpil CM3 and the rotary dial on it is meant for radar elevation control and it’s clearly jumping to a range that could cause me to miss a hit. I even tied it to an axis and the issue is still there