skypickle

Still waiting for iron flag part 2

you can shoot the balloons down....they disappear

use voice attack to move and size the kneeboard with a 1 word command voice attack is an application that allows the manipulation of the mouse cursor including clicking and dragging

now working with dns set to 8.8.8.8 and static ip and router (no dhcp)

MyPNVIS switch is now bound to some new kind of control. There are now 5 choices for it. What does this mean?

it is still happening again.

Do these switches (below the IFEI) do anything in terms of actually saving video of the flight?

In the attached track, both SLAM and SLAM-R are set to PP to destroy a T90 at the following coords. N43 46 00.55 E41 51 02.79 alt 4057 Both are set to fly a high profile. (cruise at 35k feet) Both are released within range The slam tops out at 22K feet . The slam-r at 15 k. Both are well below the high cruise profile. The slam-r hits the target. The slam falls short Any idea what i did wrong? (I dont know why the replay makes it look like my head is having a seizure. I use track ir and i really wasnt looking around that much) SLAMM.trk

thank you. oops. I should have set the wpt to ground elev

In the attached track are 2 slam weapons. The target is a T90 at N43.46.00.58 E41.51.02.73. Waypoint 2 is set to the same lat long. The first slam is set to preplanned and the above coords are used. The second slam is TOO and WPT 2 is used to designate the target. The route is depicted below. The first slam seems to hit the T90 but it is not damaged. The second slam falls short and impacts short, roughly at N 43.45.49.06 Why is my TOO SLAM missing? Why didnt the first one obliterate the T90? (Forgive the difficulty I had w the autopilot. Dont know why the jet kept rolling to the right.) SLAMM.trk OOPS, it's a SLAM , not a SLAM ER. Typo in the title.

Isnt this a bios tweak? before the OS gets loaded.

I noticed this mod fiddles with some of my keybindings. The flir and the ltd/r switch bindings disappear. What gremlins lurk in old DCS code!

Linux is growing. Win 11 is stagnant. The computer literacy of dcs players is way above the average. MY prediction is that most dcs servers would switch to linux the week it became available. Many DCS clients would switch as well to bypass the incessant crashes to desktop that the some of thirty year old code in DCS is likely responsible for. Alot of Eagle Dynamics' revenue requires putting out 'new shiny' - like airframes and maps (that are incomplete) and that is where they are putting their resources. They should consider a linux branch as 'insurance' for when windows gets pwned in a big way by chinese hacking wolfpacks. Security is on everyone's mind. Why do you think Alphabet spent 37 billion buying WIZ, a computer security firm for a multiple of its valuation?

What? You mean a G2 will now work with the latest Win 11 pro?

Αλλά είμαι Έλληνας, αλλά ζω στις ΗΠΑ. Γεννήθηκα Αμερικανός, αλλά σ’αυτο δεν φταίω εγώ.

nice skins. Do you have a discord?

to dothis i have to jump to cpg seat, change the TADS and then jump back to pilot seat I tried modifying the file C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\AH-64D\Input\AH-64D_PLT\joystick\default.lua by adding these lines: -- TEDAC ------------------------------------- { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW_FLIR, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, name = _('Custom LHG TADS Sensor Select Switch - FLIR'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW_TV, cockpit_device_id = devices.TEDAC_INPUT, value_down = 0.0, name = _('Custom LHG TADS Sensor Select Switch - TV'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW_DVO, cockpit_device_id = devices.TEDAC_INPUT, value_down = -1.0, name = _('Custom LHG TADS Sensor Select Switch - DVO'), category = {_('Custom')}}, This results in the following control options appearing Unfortunately, it does not work. Anyone have any insight into how to make this work?

I am making an overhead break practice mission and want to spawn in a jet with TACAN set to 67x and course line to 070. Is there any way to do this in the mission editor?

INITIALLY , I can switch between FXD and TADS. Turning on night vision and in PNVIS, I can still switch between FXD and TADS. You can tell I am in PNVIS mode because the night vision fluidly follows my head movement. If I change night vision to TADS, you can see the slight delay that night vision has in updating the image to follow my head position (as expected)ACQ cannot select TADS (as expected) However, if I then switch to PNVIS, in night vision, ACQ STILL CANNOT SELECT TADS. Night vision fluidly follows my head movement confirming my night vision is using the PNVIS To regain the ability to use TADS as an ACQ source when in PNVIS mode, I have to turn off night vision and turn it on again..track attached tads.trk

As a pilot, when i select pnvis in the night vision so that my ihadds is using it, i can no longer set acquisition source on the right mfd to tads. I used to be able to do this some updates ago. Note, i am not using tads in the ihadds and george ai interface is active. I cannot see what he is targeting as it (acq) remains fxd

I understand when night vision is active and set to TADS, one cannot set the acquisition source to TADS. But why can I not set acquisition to TADS if night vision is set to PNVIS? These are different sensors.

wow. i need the controls indicator and then it works as you indicated.thank you

I was starting the JSOW training seesion and was trying to set barometric altitude hold. I could not get 'BALT' to get a colon. In the attached track, you see the relevant buttons being pressed. Also, 'CPL' never appears in the saved track although I did see it appear while in cockpit. What am I doing wroing that prevents BALT from getting a colon? Lesson 25-JSOW Employment.miz_14022025_13-24.trk

Here is a better track that shows the TMR changing with the aircraft AOA. Again at some point the SLAM goes from RDY to a crossed out condition for unknown reason. SLAM2.trk

In the attached track, I set up a SLAM with the LOW flight profile in TOO mode with the target at WPT 3. Watch the large circle change size just by changing the aircraft aspect. Is this expected? Also, the SLAM then becomes crossed out and the track in the HSI disappears . I reselect the target but SLAM remains crossed out. What am I doing wrong? SLAM.trk