Tj1376

Potential Bug - A/G ordinance OSBs not clickable after Aim9X mode selected As the title suggests - once you enter the Sidewinder mode and get bit by the Aim9 seeker not displaying on the HUD, if you go back to A/G mode, the OSBs on the left display do not work. Latest open beta No mods Steps to reproduce: Air Start Stores to left DDI Select A/G mode, select J82, select efuz to inst (to verify OSBs work) Using HOTAS, select sidewinder (Lshift + S) Press "A/G" button to re-enter A/G mode Select J82 Change PPMode to TOOMode Expected Result OSB allows change to TOOMode Actual Result OSB is nonfunctional Select Efuz, OSB is nonfunctional As a workaround, unselect J82 (by pressing the J82 OSB) Select J82 OSB again OSBs are now functional Video and track file can be found here: https://drive.google.com/open?id=119mReWlX6cX54lHB7XDfpI2wZHVRAA_8 If indeed a valid bug, please move to bug section. Thank you team! TJ

He meant this link Im sure: https://forums.eagle.ru/showthread.php?t=246617 TJ

I tried multiple times this afternoon to reproduce this and couldn’t. I used 2 Fs, 2 38s and 2 12s. Positive you don’t have any mods? What loadout were you using? TJ Sent from my iPhone using Tapatalk

Question, because I Just ran into this after playing around a bit... Are you designating a waypoint as a target and forgetting to undesignate it before releasing? Ive noticed this seems to play havoc with where my weapons hit... But it does look like the Aim9x missing its seeker head after employment is an issue. TJ

This is what the hornet in DCS can do today. And if I understand, it’s how it works in real life (as close as we know without knowing secrets.) The tpod doesn’t control the F seeker- it’s not like the a10c. All the tpod does is set a target point that the F seeker can slave to. From there you’ve got to sensor select to Maverick then manually move the seeker head and achieve lock on. Once the F has locked on, it will track your moving target. It’s not anywhere near as elegant as the a10c, but with practice it works. And as I understand it may change slightly as SMEs weigh in on how it’s built in the sim today. TJ Sent from my iPhone using Tapatalk

TGP and Mav F The TPod has a POINT mode which will track a moving target. I am not certain if this is like the Harrier where the target coordinates are not updated. The MavF when locked onto a target will also track and kill a moving target even if the tpod will not update target coordinates as the target moves. Hope this helps. TJ Sent from my iPhone using Tapatalk

Any chance you can make this available again? I noticed its been taken down. :( TJ

I think you are getting your versions of Mavericks confused. Wags has done a demo of the laser maverick. But the F uses an IR seeker. There has been no video on this use, probably because while the first one works perfectly, 2,3 and 4 do not. TJ Sent from my iPhone using Tapatalk

Yeah, this is clearly WIP right now (which is probably why Wags hasnt done a video yet.) However, I've found that after you launch #1, you can get 2,3 and 4 on target by doing the following. Verify Maverick is caged Tpod SOI Designate target Maverick SOI Fly your nose to point the triangle of the MavF seeker head (in the middle of the HUD) to the diamond of the tpod target Uncage maverick Maverick will **TYPICALLY** then uncage to the SPI and you can sometimes fire at the target. Its not pretty and the harrier is still way better at this (or just using the maverick camera), but it can be done. TJ

Because I hate re-entering coordinates if they happen to vanish. I also enter a waypoint coordinate to get there, so why not just make it a target too? And finally, my mission has me attacking and rearming bases that have 30ish targets. By using the waypoint feature I can remember which target I’ve attacked. Last point- TOO is only slower on the first four bombs (You can’t go pickle pickle pickle pickle. It’s pickle, next waypoint, waypoint designate pickle next waypoint, waypoint designate.) Easy to setup bindings on Hotas to do this nearly as fast as PPs first four. The second four are similar in speed (for now as you have to step to PP2.) TJ Sent from my iPhone using Tapatalk

The coordinates in the F10 map are in DDMMSS while the HSI input is set by default to DDMMmm. So unless you are converting your coordinates before input, you might be missing your target. So, try this to see if it fixes you: From the F10 map, make sure you are getting PRECISE coordinates, use ALT + Y to change your coordinates to precise. Jot down the PRECISE coordinates (after MGRS - will look like N26-31-47.58 E53-59-49.07 117ft) Start your jet On the HSI go to Data Go to AC change the default entry in the bottom right from LATLONG DCML to LATLONG SEC by pushing the OSB on the far right, bottom side Now input your waypoint coordinates in the HSI Take off, warm up the weapons, navigate towards waypoint Designate the waypoint as a target TOO mode on the JSOW Go to the mission screen of the JSOW Verify the coordinates on the JSOW display match the coordinates on the target/waypoint If all matches, fire away, see if you hit the target. Report back your results.. If you missed, please upload the track file so others can help. TJ

There was a great thread about this four months ago - a quick search of Tunguska brought it back as the third search result. Not sure if the link will copy properly with Tapatalk. Just try the search and you can find it. SA-19 no MWS or lock on warning? https://r.tapatalk.com/shareLink?share_fid=74365&share_tid=215196&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Ft%3D215196&share_type=t TJ Sent from my iPhone using Tapatalk

Tunguska fires in all weather and typically doesn’t rely on optics unless the target is danger close (I can’t watch the track, so not sure if that’s the case but I assume you weren’t because you were above the clouds.). Tunguska can track multiple targets and engage multiple targets- this means it’s launching in TWS. In DCS, TWS doesn’t provide any launch warning unless your airframe is equipped with MWS (like the a10c.) The f18 we have is not so equipped. http://www.ausairpower.net/APA-96K6-Pantsir-2K22-Tunguska.html These little guys remain one of the most deadly threats in DCS. TJ Sent from my iPhone using Tapatalk

Have you tried TOO mode? Yes it’s slightly slower for the first four bombs, but it’s 100 times easier (imo) to input as waypoints and use TOO. Just make sure you change your HSI input to DDMMssss instead of the default DDMMmmmm. TJ Sent from my iPhone using Tapatalk

I think it’s also used for your wingman’s targets. In the event he can’t put shots on target and his targets are more valuable, switch your mission to PP2 and fire away. TJ Sent from my iPhone using Tapatalk

With TOO mode you need to make sure you are entering coordinates into the HSI as DDMMmmmm (this is the default when the f18 loads.) If you’d like to enter DDMMssss (which is what the f10 map displays), you need to go to the hsi, go to data, A/C and then in the bottom right hit the push button for LATLONGMIN (or something like that) and it will change to LTLONGSEC (or something similar.) Now enter your coordinates into the HSI in DDMMssss and when you use TOO mode the bombs won’t automatically convert what it thinks is a DDMMmmmm into a DDMMssss. Give it a whirl and see if it fixes your too issue. TJ Sent from my iPhone using Tapatalk

Ahhh... This is why Chucks Guide doesnt match - and since the manual has no mention of the format (or if it does I cant find it), thats why we have been left astray. Thanks guys I successfully put 12 jdams on targets tonight in my practice mission using TOO mode. TJ

And I just changed my HSI to LATLN SEC (Data, A/C, bottom right) and entered my coordinates again via UFS in DDMMssss (precise) then went to the JDAM and hit TOO mode. PRESTO, perfect coordinates for the target. hehehehe - i love bug reports (i have 15 years of software development in my professional career) - the only gurantee as you peel back the layers of the onion is that everyone cries. This sure doesnt seem like a valid bug now: https://forums.eagle.ru/showthread.php?t=243322 TJ

Well crap - you sir are exactly right (I think) So I filed this bug report a few days ago: https://forums.eagle.ru/showthread.php?t=243322 In that bug report, the TOO mode for JDAMs isnt taking the coordinates (entered as DDMMSSSS) from the HSI and transferring them over to the JDAM correctly (its converting them and as such the JDAM misses the intended target.) See, I think the way its intended to work is by default you enter into the HSI DDMMSS, and then on the DATA page of the HSI, it shows DDMMmmmm (it converts to this format.) That aligns with Chucks guide (all though I cant find anything in the early access manual to confirm.) However, when you enter the coordinates in DDMMSSss (precise), the HSI isnt converting them at all - its displaying them raw as you entered. Thats odd, as 169 of Chucks guide clearly shows where he entered DDMMSS and it was converted to DDMMmm. So as a little test, this is what I did: Took my coordinates from DDMMSSSS and converted them to DDMMmmmm: 26.14.48.21 54.30.47.06 to 26.14.80.35 54.30.79.01 I then punched those into the HSI (26.14.8035 54.30.7901) and selected TOO mode on a JDAM - now the JDAM shows 26.14.48.21 (PERFECT) 54.30.47.41 (very close) So, I think you are actually on to something... I think somewhere either we are suppost to enter DDMMmm into the HSI (like you describe) or the HSI has stopped converting DDMMss to DDMMmm. TJ

Where do you think the HSI takes DD MM mm? I don’t have access to the manual at the moment but Chucks guide on page 169 lists the HSI as DDMMss. TJ Sent from my iPhone using Tapatalk

The post directly above yours reads: Sent from my iPhone using Tapatalk

I just got a notification from 9L that they have confirmed this is a bug and have reported it to the team. If you go back to the bugs section you can see the update. TJ Sent from my iPhone using Tapatalk

As a guy who almost never posts here, Ive very recently had both a very good and very bad experience with the current bug reporting system 1) I posted in the general DCS F18 forum to ask a question on what I was doing wrong - this post automagically moved from the DCS F18 forum to the DCS F18 bug sub forum and the title was changed as "Reported"and the thread locked down - my initial reaction was "too cool!" but I received no notification about this. I had to go back to find my post. Because the post was locked down, no one could comment on it so I wasnt getting notifications and when the admins moved the post I also received zero notifications. While this was VERY effective for the admins, as a customer it left me both excited and puzzled as had I not found my old post via my transcript (it wasnt in the DCS F18 forum where I posted it anymore!) I would have never known what happened. You can read this thread here: https://forums.eagle.ru/showthread.php?t=243322 2) The above encouraged me to post another bug report - which left me feeling frustrated. This second bug report was closed as "NOT A BUG" with zero explanation. So again, with zero notification on who made the update to my post and with zero information on why my bug wasnt a bug, I was left feeling puzzled. This post has now been merged with another post (which is a good thing!) but if I give you the url to it, it wont make any sense because the two posts were merged. You just have to trust me that I made a post that said "here is how to reproduce XYZ bug" and the title just changed to "NOT A BUG" and the post had no explanation. Im not here to criticize the admins - like Pikey said earlier, its probably mostly all noise to them from internet warriors who wont read the manual - it probably gets very mundane and repetitive. But for the people that actually try to make DCS a better place, the current system lacks a feedback mechanism to help encourage good reporters to report. Id almost recommend no one can post in Bugs until they meet a certain threshold granted to them by the Admins. And those people can move posts from the main forum to the bugs sub forum. Then maybe the Admins can spend time with those few people to educate them on the bugs report and how to research and those 'volunteers' can educate the community. Man, I'd attend a weekly call even if it was at oh dark thirty to walk through a handful of bug reports and learn the reason behind them. That could be very powerful! Anyways, just my two cents from a guy who dealt with this very recently and walked away both in awe (MATT WAGNER COMMENTED ON MY POST! HOW COOL IS THAT??!??) and frustrated from the whole experience. Good luck with the direction this goes - I wish you all well! TJ

Hey sorry- Im just trying to learn. Please feel free to move this thread back! Here is where I struggle: If the elevation for the coordinates of the JDAM is AGL (above ground level.) - In all of Wags videos on this topic, he enters an elevation in the JDAM or JSOW- the elevation he enters must be the MSL elevation of the target (his static airplanes on the ramp for his latest JSOW video are not sitting 43 feet above ground level (AGL) - or put another way, his static aircraft are not sitting 43 feet above the ramp. - reference 1m 36s of the video. Also, I was under the impression that the F10 map only provides MSL data? (this is where I get the data to enter elevation) I totally understand if you want to say "well the way we designed it is for MSL elevation of non zero numbers and its working as designed." Ive spent 15 years now in software development and I can totally understand this statement. But Im also wondering if Im missing something - in which case I really want to learn what and how and why! You guys are the defacto experts on this matter - can you help us better understand how this tool works? Its really interesting stuff! Thanks for everything you guys do to build such an immersive simulator where we can discuss these fine points! TJ

Wait- the more I thought about this, the more this doesnt make sense If the elevation of the target was in AGL, wouldnt all entries for targets on the ground be 0 feet/meters? Are we positive this is AGL? Ive been using MSL elevation for quite some time.... TJ