JIGGAwest

Would you share your monitor Lua? I have a feeling this is linked to the viewports.center command

Flat screen user: This is also a problem for me. My George AI is center of my screen on top of my HMD reticle. Drives me nuts... Too much going on. I was hoping to dig through the folders to find the variable name so that I could change it in the monitor config Lua. Hopefully Just like you can with the jester ai menu.

I am also only seeing the CPG MPD's when I'm starting in the pilot seat with stock settings for RIGHT_MFCD and LEFT_MFCD once renaming the variable try_find_assigned_viewpoint() for MFD_cpg_left_init MFD_cpg_right_init, I used AH64_CPG_RIGHT and AH64_CPG_LEFT also changed MFD_plt_left_init MFD_plt_right_init try_find_assigned_viewpoint() to AH64_PILOT_RIGHT AH64_PILOT_LEFT I added all variables to my monitor config lua. The CPG still takes priority over the pilot. only after commenting out the AH64_CPG_RIGHT and AH64_CPG_LEFT can I see the pilot MPDs in my monitor export. I have not experimented with alternate positions, so that they don't conflict in the same position. But, that wont work with my simpit. Additionally, anyone know where the equivalent TEDAC folder path would be? I'm not getting the CENTER_MFCD working like the F18. Or what the Variable is named?

Is there a monitor lua command for centering the Petrovich menu like the jester menu for the f14?

sorry, very difficult to watch tracks. And it looks like I was a bit off in my range estimates. I'm curious if anyone else can get longer accurate ranges... I was able to do a test. I could drop at about 14.6nm 32k feet. it was marginally successful damage, but not a direct hit. subsequent drops showed similar results. The most accurate drops being 6-12nm at a high percentage release cue. I'll have a youtube video uploaded if you would like to see the results.

I'll run some tests and post a screenshot. I may also be lofting near the release cue to grab little extra range. I know for sure I'm releasing at a higher altitude than your typical drops.

What speed and altitude are you making these attempts? I can usually get +15nm releases above 28k feet.

Well, I'm sorry to hear that. I guess I've been lucky recently, which previously, was not the case - at all. Minutes of usage would cause this errors. Personally still have not recently seen an issue. I play dcs for hours a day.

might have some good news to report. It seems with the latest Radeon drivers 21.9.2, I've not experienced any f10 UI element issues. Although, I haven't spent much time in combined arms to know for sure with extended use. But, normal airframe usage seems to be working well.

See if this helps...

I'm so frustrated at this point. This is such a game breaker for me. AMD 5900X / Radeon 6900XT 64GB ram This issue has plagued many users for months and months. I understand wanting to fix this by understanding why this happens. But, in the meantime... Please DEV's, please..... Please.... Would you instead implement a UI elements reset function .... Thank you, I would be forever grateful. And again thank you for you artistry and hard work. I love DCS!!!

The tracks are red. But I had continually tested this several times over a matter of days on blue as well. But, for sure red was an issues with satnav. I may have had other issue while testing on blue. Things that could have been going on: - unrestricted satnav not enabled - possibly did not designate the TPOD prior to using TOO mode to create target points. TOO creation would have been made while in MAP DES mode. (Creates a severe error in drops, not sure if bugged) - the TPOD bug, where no coordinates are displayed, shows only 000000000, could have been present while selecting the targets, thus no gps point created. I've since learned to work around the bugs and my mistakes. Although, I have mostly played with unrestricted satnav enabled missions. There will be a few times where the drops don't happen correctly, but I cant exactly lock down the issue, possible desync?

still a persistent bug for DCS 2.7.5.10869 Open Beta - 11.08.2021

I was flying RED with Unrestricted SATNAV was set to false, this was where I was seeing the issue. could this setting have been affecting the blue side as well? Because I seemed to have similar issues.

With a recent test, I did find the JDAM's are indeed working and accurate. 10 TOO targets, TPOD DES, 9 hits, 8 kiils out of a 10 JDAM ripple. The multiplayer mission I was flying on did not have the Unrestricted SATNAV flag checked. One the flag was checked, JDAM's were working properly. {BUG} The TPOD problem still exists for showing the coordinates. first activation of A/G mode and the TPOD will result in 00000000 coordinates. Using DESG on the EHSD page will not function correctly. If you hit A/G a second time the TPOD corrects itself and coordinates will appear and EHSD DESG works. {BUG} With previous updates MAP DESG would still allow for somewhat accurate JDAM drops. With the current update MAP DES on the TPOD will result in a severe error in coordinates and JDAM drops. You must use TPOD DES to get an accurate JDAM drop. I am not sure about the modeling of the GPS guiding or why Unrestricted SATNAV should be required. But once this is active I'm not seeing anything near 30m, maybe more like 1-2m.

Thank you for the suggestion. I'll try to get the mission designers to update this. the date is 2021 shorter track has been added above.

Hello, I've tested this multiple times. There seems to be some issue with the TPOD. Part of the issue is the coordinates not populating when targeting ground targets. The other issue is the TPOD pointing at the sky instead of the ground on EHSD DESG button press. The master modes seem to have the issues regardless of the mode. Sometimes switching the master mode or cycling the waypoints or TGT points will allow the coordinated to populate on the TPOD. Regardless of the coordinates populating or not THE GPS guided weapon GBU-38 does not hit targets. Attached is a track file from a multiplayer server, date on the mission is year 2021 https://drive.google.com/file/d/17uXvpeRcxZ129m9-6FG-u8lPcMPJuH8M/view?usp=sharing

Hello, Since the recent update DCS 2.7.4.9847 I've been having trouble with the TPOD TGT points. I have flown probably 20 ground target bombing missions, maybe two flights were trouble free. issue: - GBU-38 (possible issue with GBU-54 also) do not hit designated target, they fall in a zone but not accurate enough for ground units. factors: - Multiplayer use - no waypoints loaded for harrier on hot start possible causes: - desync ? - not visually designating target correctly - TOO TGT point designated while in TPOD MAP DES / SLV DES mode (not in TPOD DES mode) - BUG ? - during alot of the tests I previously was not designating the targets and the TPOD mode was MAP DES / SLV DES - this did not cause much issue in previous versions. But, now I do not use MAP DES for target points any longer. - Assigning TGT points too far away ? attached is a track of a mission where I believe I did the JDAM process correctly using both TOO assignments for JDAM ripple drop and WINC (waypoint increment) for single designated drops. TGT points are assigned at less than 20nm. For JDAM ripple, process was: - A/G mode - activate TPOD SSS down x2 - TDC DOWN / action position (special option is selected in game settings) - verify coordinates are visible on TPOD, and TPOD MODE is TPOD DES - use UFC TOO button, verify TGT point number, hit UFC ENT button - Master arm ON - set FUZE JDAM to IN - fly to in range cue, wait for high percentage accuracy, then hold weapon drop until all selected TGT points drop off the HUD For Single target: - Master ARM ON - set FUZE JDAM to IN - activate TPOD SSS down x2 - TDC DOWN / action position (special option is selected in game settings) - verify coordinates are visible on TPOD, and TPOD MODE is TPOD DES - use WINC, look for N0 on HUD - fly to in range cue, wait for high percentage accuracy, then hold weapon drop Shorter Track https://drive.google.com/file/d/17uXvpeRcxZ129m9-6FG-u8lPcMPJuH8M/view?usp=sharing Sorry it's a long track. 3 flights. Link to track 69MB https://drive.google.com/file/d/1GPZevghNzNBJLt2-3OBwcp6Zta6dyfWd/view?usp=sharing

Hello, The MPCD button that designated the TPOD FLIR mode for black hot or white hot does not change the setting. Sensor select switch (short - right) does work, but the MPCS button does not.

<TEST FILES> see files in first post. looks pretty good. ****reserved for comments******

I'm curious if you have had a chance to try fidelityFX personally? I have a top 1% spec PC (Ryzen 9 5900x / sapphire 6900XT). I run DCS 4k with an average of 88FPS (max settings.) I tried fidelityFX CAS with cyberpunk, subjectively, it works amazingly well. No instance of blurriness.

There problem still persistent in version DCS 2.7.2.8165.2 Open Beta, I have not confirmed in latest DCS 2.7.3.8494 Open Beta.

I found out the cause was multi monitor. I have one large main display as the main render and one small monitor dimensionally positioned under the main render for MFD exports. If I unplug the second monitor the problem goes away. While your solution works to center the reticle in the view, it seemed not to work for petrovich targeting. The major misalignment is still there.