Habu_69

Bug, or feature? DCSW 2.7.2.7910. On both the ME and the in-game F10 map coordinates show, apparently, the elevation of the sea bed, for example -1500 feet off Syrian coast. Perhaps this is a feature for underwater objects?

Look at the file: DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\Macro_sequencies.lua It is a script that, when it is called, runs cockpit clickable functions for aircraft start-up. I should think it might be possible to adapt its format to achieve your goals.

Anyone compared ED's reworked Caucasus ground textures to either Taz or Barteks's mods?

Thank you for the very useful tool you have created. Another feature that would extend its functionality is the ability to transfer PRECISE waypoints. All in good time, I am sure.

DCS 2.7.1.7139. Win 10 21H1. PG Map. When FLIR is turned off using the mouse on the cockpit switch, the TGP LOS symbol on the SA page disappears, as expected. However, when FLIR is turned off using a controller app Key-bind, the LOS symbol remains visible on the SA page. Track attached. TGP LOS.trk

i omitted on purpose for this trial. I noticed none of these commands included the "i". I have successfully customized the auto-start sequence to a considerable extent. Mirrors ON command must be hard-coded into one of the earlier commands. Interesting challenge, especially no device name anywhere I could find.

Mine was delivered today as scheduled. Shipped from Plainfield, Ind. USA to WV. No issues setting it up and flying in DCS right away. I found headset slightly heavier and warmer under use than G2, but not to an uncomfortable extent. Audio and mic are fine for DCS. I am listening to jet noise and military radio, not Beethoven. Colors are appreciably more saturated and FOV wider than G2. Res/clarity about the same. Sweet spot smaller. I will repeat others: if you are having no issues with a G2, I would not find value in an upgrade. Just regarding DCS VR in general, while the immersion factor in VR is a major level above a monitor, VR has far to go to approximate the visual detail and screen brightness a monitor provides. For example when landing on a carrier, I can't distinguish the approach centerline until almost at the ramp. Visually acquiring a particular factory to bomb in an industrial area is impossible for me: the buildings all blend together. The visual image appears less bright. Perhaps if I am ever able to buy a top graphics card (stuck with a 2070 Super for now) so that I can bump up the DCS graphics settings, these VR shortcomings can be satisfactorily mitigated.

Not exactly a key-binding issue, but the Hornet auto-start sequence can be customized by altering the macro-sequencies.lua file in Cockpit\Scripts. During the sequence the cockpit mirrors are toggled on. I wish to add a line to the macro to toggle them off, but so far, no joy. A typical auto-start command looks like this: push_start_command(dt, {device = devices.OXYGEN_INTERFACE, action = oxygen_commands.OBOGS_ControlSw, value = 1.0}) dt is simply a defined delay time in sec. Defaut.lua key assignment command is thus: {combos = {{key = 'M', reformers = {'RWin'}}}, down = iCommandToggleMirrors, name = _('Toggle Mirrors'), category = _('View Cockpit')}, I can not find a device name for the mirrors, but have tried several variation of this line: push_start_command(dt, {action = CommandToggleMirrors}) Looks like this SHOULD be simple. Any suggestions?

Advantages over the similar The Way mod are that WP Editor includes WP elevation and weapon delivery coordinates. The Way allows direct input from F10 map in game.

I devised a procedure for handing off radar SEA target to TGP that works: 1. Set up AG, GBU for ship attack. Stores in LDDI, surface radar in RDDI. 2. Radar SEA mode in RDDI. Find and designate target (SCS right). 3. Switch radar to LDDI. TDC pri to LDDI. 4. Invoke FLIR on RDDI. Should be tracking radar target. Go narrow FOV. Keep TDC priority on LDDI. 5. Arm laser. 6. At about 15 NM, SCS right X3 quickly. Moves TDC to RDDI and reacquires moving target track | | symbol on TGP. 7. Follow HUD cues to deploy LGB. This works consistently for me, but may not be RL protocol. Track attached. SEA GBU Success.trk

Appreciate your interest, BN. Guess we need advice from a Hornet pilot or technician. I would point out that logic SHOULD dictate that moving SOI from AG radar to slaved TGP would not cause the TGP to lose track. Radar losing track (due to gimbal limits) when TGP has a slaved target should not cause TGP to lose track. When switching SOI from TGP to AGM-65F the seeker does NOT lose track. Perhaps some other mechanism we are not aware of applies. My .02 USD.

If I use my Vive Pro2 only for DCS, do I REALLY need a Vive controller?

I believe TGP was in PTRK with |< >| symbology. If pilot tries to change it, tho, TGP drops track as soon as TGP DDI becomes SOI. You can see this in the .trk file. Well, no way the radar is NOT going to exceed its gimbals before the weapon makes impact, so the standard turn-away has no bearing on this issue.

Working with HTC support regarding their website PW reset, they advised that my Vive Pro2 would be shipped this week. Ordered about May 20.

Potential bug, but may be related to other radar/TGP bugs. In SEA mode tracking a ship with radar, the TGP appears to lock-on to the radar target; however, when the radar loses lock during target overflight, the TGP also loses lock. This occurs so late in an LGB weapon delivery procedure that reacquiring lock with the TGP is seldom achievable. A procedure that works is to switch SOI to the TGP DDI earlier, whereupon the TGP immediately loses lock. Pilot can then reacquire lock with the TGP and deliver LGB normally. Another strange behavior is that when SURF radar is assigned to right DDI and TGP to left, TGP can acquire lock on a med sized ship no further than 10 miles. With TGP on right and radar on left, TGP will acquire the target at 15 miles. I have repeated this behavior many times. Track attached. DCS 2.7.1.7029 SEA GBU Lost Lock.trk

Reinforce the radar picture by constantly updating your geographic situational awareness. Then I try to visualize a map that includes 3 locations: the bullseye in the center, my aircraft location and heading with respect to the bullseye, and the target location based on bearing/range from the bullseye. Then I can estimate/visualize the target's general bearing and distance relative to my own position. Becomes second nature with practice.

My buy decision was based on frustrating experience with G2 and AMD X570 chipset.

Does this mod add WP to an existing flight plan or replace the existing FP with new WP's from the map markers?

Am I correct in thinking that a Vive Pro 2, since it functions without WMR, makes that 2 GB of VRAM available to DCS?

I also gave up on the G2 after about 3 months of troubleshooting with HP. To HP's credit they gave me a full refund. I was a victim of WMR failing to recognize the headset, with X570 mobo. Believe me, I tried every published trick and hardware accessory. Now, I realize my experience was atypical. YMMV.

I strongly support having the ability to use voice comms to interact with the ATC. Having to rely on a menu system for communications is a huge immersion-killer. Hence the enormous popularity of programs like Voice Attack. Yes, Voice Attack can be programmed to manipulate the menu system, but only to a limited degree, as objects like airfields seldom appear in the same order.

Don't know. I started using the direct edit method when the snapview saving procedure failed to permanently alter the VR and monitor default views I wanted. Playing with the FOV and y_trans (seat height) values got me there.

Try OvGME

Supercarrier group templates with flight deck objects do exist. Search the Mods forum and User Files and download them. In the ME add the desired template.

I edit the Snapviews.lua file in the Saved Games\DCS.openbeta\Config\View\ folder. Snapviews for FA-18C start at about line 2444 and item [13] is the (non-VR) default view. Try setting the viewAngle to about 70.