Recluse

Really? Got a link for that? Uninstall OXRTK completely or just disable?? I noticed that it was disabled when I first went into VR, but then I enabled it. Had a rough VR time in Multiplayer maybe this is why? Darn, I REALLY REALLY REALLY liked having the OVERLAY in addition to everything else. Maybe I will turn everything BUT the overlay off

Thanks for the confirmation. FYI, I tried to reproduce your screen shot from the F86FC to better compare: Didn't match the time of day.... sorry..

No, it is a glitch that occured for some due to the conversion of the PACK to the individual aircraft. It will be fixed according to @BIGNEWY I seem to be one of the very lucky ones who had no problem (yet... LOL) null

Hmmm.... F86FC cockpit looks kind of off...Mirror hanging in the air and slanted HUD glass? Don't have the Full Fidelity F-86 so I don't know if this is "Correct as is" EDIT: OK looks like the "Sighting Glass" is correct at an angle, though it does look a bit more angled than the picture in the manual. Mirror still bugs me

FC4/FC 2024 doesn't show up (for me) as a discrete option. Only the individual aircraft. Also, I note that in the DCS Folder structure, all of the aircraft used to be nested under a FLAMING CLIFFS folder, but now that folder only contains two folders (COCKPIT and MISSIONS) while all the other stuff is in separate folders for each aircraft. Similarly, the SPECIAL tab used to have all aircraft nested under the FC3 tab but now they are all individual. Maybe because I didn't (re)-Install Flaming Cliffs 3, but as everything was working fine with my FC3 aircraft, I didn't want to Break anything.

All of mine were fine, but along with the option to install the 3 new aircraft, I had the option to install FC3, but I just installed the new aircraft separately. Now I have all of them, but listed separately and FC3 is still in the AVAILABLE TO INSTALL. (Previously I installed FC3 and not the individual modules, BTW and FC3 showed up). null

Use your DMT or TPOD LSS/ LST to pick up the spot, then designate it as T0 (or another Target point) so you know when to drop. You can eyeball it without a designation to make sure the GBU-54 is in the basket, but I think the GBU-54 needs an initial TOO or PP drop point to get release cues. Never dropped a GBU-54 as Laser Guided Only, but since when self lasing you usually have designation anyway, it isnt really a thing. A bit different with JTAC.

Don't know if it would be helpful or not, but the JTAC (REAPER) functions in FOOTHOLD have this ability. You can step to the next target or have them prioritize the type of target with the F10 Menu. Seems to be included in Zone Commander.

Same thing happened to me. I had to un-quarrantine the file and add the DCS top level folder to the EXCEPTIONS list. FYI the file is: null

See this LOADOUT REWORK post for some more information: For example, you will notice that you cannot have Sidewinders or Sidearms on the wingtips if you have 2 JDAM on the adjacent pylon on the \ configuration that puts them close to the wingtip, but you CAN with the / configuration.

Same here.... with 6 CBU-97 on one CFT.. Program to RPL SGL, QTY 6. INT 300 I dropped on on a Target of Opportunity and forgot to crank the QTY down to 5 for the RPL SGL program release. IMMEDIATE CTD upon release. Happened in Multiplayer. Will try to reproduce in SINGLE player and provide a TRK..

We have been flying a version of Foothold on the Sinai Map... It is indeed very demanding, though I don't know if it is the number of units or the terrain itself. The server we ran Foothold Caucasus (and SYRIA, IIRC) on has 24 GB RAM, and it ran fine with that map, but SINAI brought it to its knees. Hosting on a client machine with 32-64 GB seemed to work fine. There are ways to set up AI helos to pick up troops in the Mission Editor, but it all has to be orchestrated specifically and I would guess it requires more Scripting to add any dynamic aspects to it. The aspect I can see that makes sense is to dispatch an AI helo to pick up a downed pilot at a certain location...especially if no humans fly any helos in a mission.

I could be VERY WRONG, but I don't think there is a specific JTAC unit in DCS that is recognizable. It has to be infantry with a "lase" order. So not sure you can include a "JTAC" in a spawner with other units who arent supposed to lase. So, I think the non-requestable comes from having an entry in the list that is not in the legalTroops variable (and in fact doesn't exist in DCS) As an aside, I have found that if I spell a unit wrong, like "SoliderM249" instead of "SoldierM249" it seems to generate a LEOPARD by default.

I find myself going old school sometimes as well when I KNOW DML can do it and do it better but I just don't know how.

@DD_Friar In mine, they aren't spawning at mission start. That's why I thought that your spawnUnits? flag might be getting triggered somehow at mission start through some other event. I get what you are doing with the random flag, but if they are REQUESTABLE at each location, you shouldn't even need a flag. OOPS Never mind! DIfferent scenario... still worth checking if there is any initialization of the flags at mission start. Try taking OUT the flag and see if they are still spawning at mission start. I think you were on the right track before with a pause? But maybe you need an Activate as well before the spawn? flag will work?

@DD_Friar I built a quick test some time ago and it seems to work fine. The troops don't spawn until I request them from one of the aircraft. I think the problem might be with your spawnUnits? flag which might be getting triggered prematurely. I don't think it is needed when the Requestable option is there.

The Strike Eagle has some complicated Navigation logic compared to other aircraft. For the TSD PB 9 (Bottom row, 4th from the Left is used to select ROUTE A, B, or C for Display. In your screenshot, you see the A there which means ROUTE A is displayed. The route in the F-15E are A B C the 2 represents the Steerpoint, so 2A is steerpoint 2 on Route A. "B" alone is always "STEERPOINT 0" and gets you back where you started. You will not get a route to follow if "B" is selected. IF you are following ROUTE A, you should select "1A" in the UFC. You will then see the circles in the HUD starting with Sequence Point 1 and it will auto switch to the next Sequence point (if this option is selected). To select a Steerpoint on the UFC, type in the number and Route, e.g. 3A will get you to Steerpoint 3 on ROUTE A. Be careful, because if you have TARGET POINTS you need to put a . after it. Once you have a Route in a selected Steerpoint in the UFC, it assumes you want to stay on that route So if Steerpoint 1A is selected, entering 2 will get you Steerpoint 2A. 2. will get you Target Point 2.A It may be good to uniquely specify it... 3C will get you to STP 3 Route C. IF a steerpoint doesn't exist you can create it. Scratchpad basically automates the button pushes. See the Manual: (or find any one of a number of good YOUTUBE videos. For this reason, when I use ScratchPad to enter Targets for JDAMS, I usually do it for ROUTE C, so I can use Route A for pure Navigation. Several ways to do this with ScratchPad. In the DRAKEN 35 README file there are instructions for entering a starting point (WSS) or a specific WP on the # for each Coordinate (WDES) Examples from the README: Set WSS to point 2 of route A: @<2A> Set WSS to point 1 of route C : @<1C> @|#|N 41°39.650'|E 041°50.063'|2462| -> will load in the next point of the sequence/route @|#.|N 41°39.650'|E 041°50.063'|2462| -> will load in the next TARGET point of the sequence/route @|5B|N 41°39.650'|E 041°50.063'|2462| -> will attempt to load the point in 5B @|3.A|N 41°39.650'|E 041°50.063'|2462| -> will attempt to load a target point For example, what I do when I create TARGET POINTS in route C is to enter: @<1.C> at the top and use the @|#.| for each coordinate. If I wanted a pure NAV point vs. Target, I would just leave out the .

You need to first click the little box to enable the white Dot. Once the box is checked, the +L/L will appear to insert the coords. Note: In my example below I already had some coordinates in from a previous session.

Thanks @cfrag for the detailed explanation! Makes sense.

@cfrag Don't know if this is feasible, but a little enhancement suggestion: - I have been enjoying the heck out of Willie Pete. Being able to call down the Steel Rain has been a huge force multiplier in our Foothold adventures!! As you well know, there are issues when WP initializes with GROUPS of aircraft, and issues when aircraft in groups are trying to perform the FAC role. I've taken to creating dedicated single FAC aircraft to carry out the duty. Still, when WilliePete initializes, it does a ton of work and, when Verbose, sends a TON of messages about trying to initialize Groups. Wondering if it would be possible to add a Configuration parameter for the NAME of an aircraft Group or Unit, so, for example, WP would only initialize aircraft in a group (or an individual unit named *FAC. For the UNIT designation, for example, you could have a group, "Harrier CAS" and, let's say Harrier CAS -3 had a unit name of Harrier CAS-FAC. That way, WP would initialize only that aircraft to perform the role and ignore the others in the Group. If it has to be GROUP based, they you would still have to create a separate aircraft in a Group named "HARRIER-FAC" but the overhead during the initialization process would be significantly lower (unless the work of parsing out specific names would be even MORE overhead. Maybe I haven't though this through, but presenting it for your amusement if nothing else

Agree on all points. Laser Maverick E/E2 similarly a nightmare of switchology, at least when using the TPOD for the E2 Piece of cake when someone else is doing the Lasing!! My favorite Harrier Weapon is the APKWS... much easier to use!

It was hard to tell since the .trk cut off, but when you bring up the MAV WPN video, you need to do a SSS UP to put it into IRMV mode, and then you might need to do another TDC Depress to lock it (Crosshairs snap to target). I took control and this was the case. The Maverick wasn't in IRMV mode.

I noticed something when I posted that screenshot. I never THOUGHT TO use it, but I saw that the COMMAND MENU RETURN function (which I have bound to TRIM LEFT) turns off the Menu just like the Second press of the COMM 1/COMM 2 SHOULD DO. So, you only need ONE binding to get you back to a menu removal. No need to scroll all the way down. Agree that it would be good if it just worked like other Aircraft, but the addition of that COMMAND MENU is a great Quality of LIfe improvement, especially for VR!!

This is true, as opposed to most (all?) other aircraft. You CAN, however map the new COMMAND MENU bindings for scrolling through the Comm menu and selecting the EXIT function. I use my Trim hat which works fine while the comm menu is on screen, but I have to always be careful not to ACTUALLY need to TRIM while the Comms menu is up! null

I am resurrecting this thread. Last night I was in a Hot Start F-15E with NO steerpoints set, yet, with Bullseye at "BE01" the Bullseye showed up on my Radar in exactly the spot it was on the F10 Map. I added some Steerpoints, and, following the manual tried to Change the Bullseye by typing a number into the Scratchpad and clicking PB8 with BE01. As mentioned above, NOTHING happened, but I am thinking maybe nothing SHOULD have happened. I saw some posts over in the Discord that lead me to believe that BE01 doesn't really mean Bullseye is at Steerpoint 1, but that it is the location of "BULLSEYE 01" however that it set. In the Discord, they seemed to suggest that "BE01" is a discrete steerpoint outside the other routes that can be edited as a "normal steerpoint" but I did not get a chance to try this. Can someone from RAZBAM confirm or deny the BULLSEYE LOGIC one way or the other?