045

I have reproduced and taken screenshots of it in the first mission we noticed it in, this better shows the disparity and this track file is small enough to fit. The differences this time were that is was in singleplayer, I didn't have the identical loadout, didn't do my fire tests and my jet was invisible, but the results were functionally identical. The F10 view shows the location of the waypoint as entered in the mission editor. The distance between the point on the ground the Mav's seeker head auto slewed to is about 3km, but what I found interesting is that the point got closer to the waypoint as my jet closed, almost as if it were looking at a point below the surface (why I originally thought of the Ka-50). To clarify, I did undesignate, cage my Mav and used waypoint designate again with the same results. Hornet Wypt Dsg.trk

I have attached the first mission file to this post. The track file is too large unfortunately. 26th 1989-DEAD - Operation T-Off.miz

In a past mission, I noticed waypoint designate caused my Maverick to slew well short of the waypoint (almost like it lacked elevation data like in the Ka-50's PVI-800 Nav Tgt system). Then later that mission when doing an auto bombing run, my bombs fell remarkably short and wide and in a similar manner to how the Maverick's slew deviated. The bombs missing by a similar margin is what made me think it might not have been pilot error. I checked the track file but it had me run into the drink well before that point (which totally didn't happen... this time). I tested it on another mission and took the attached screenshots. The offset from the waypoint is less extreme than I remember in the first mission, but that was a stressful mission so I might be misremembering. I am attaching both mission files and the track file for the first mission in question, just in case it's a fault of my computer that the track deviates from the original. Anapa - Multi-Practice - Wypt Inaccuracy.miz

Didn't Wags have an Iraq module icon of some sort at the bottom of one of his live streams? Iraq-Kuwait would go well with all the Gen 4 jets available/incoming. Then again Iran-Iraq would go better with the Su-25T, the one free jet, though obviously that'd still be fictional. A Cold War era European map would definitely have great potential, but I imagine that'd be pretty elaborate for a free map.

That is good too know, thank you, but darn I guess we'll have to go without. Can you link where you found out from (if from the internet)? I like to keep a database of useful sites for campaign making.

My brother and I are playing the Hornet mini-campaign, expanded to be indefinite length and dynamic. I'm trying to emulate how the Soviet Union might combat our carrier group and the formidable Phoenix missiles using tactics like low level GCI led intercept with radar only for attack, and of course the Soviet's biggest advantage, numbers. Since right now there are only two of us, we are using AI flights in great numbers for both friendlies and hostiles. It is working well, but obviously radio overload can be a problem when your side has AWACS and WWII rodeo numbers of flights. Finding a balance between too much and too little information is obviously ongoing. It gave me the idea of AI aircraft giving Fox calls when they fire the appropriate missile. I know AI wingmen will call Fox 1, etc. so the voiceovers might already be in place. I would find this useful as having AI flights report when they engage bandits can quickly cause radio overload, especially when those flights are on Search and Engage in Zone tasks and the bandits enter and leave said zones multiple times. The Bulls call is useful of course, but can sometimes clog up the radio due to its length. A short call such as "Chevy 2-4, Fox 3" would be really helpful as I'd know I set up our AI properly, that we have cover as we go do our Hornet things, and hearing a "Chevy 2-4, Fox 3" and seeing a contrail from out to sea would tell me "Ok, that's most likely a Phoenix going out". In closing, I'd like to state that while playing this campaign, I'm really glad the Cold War never got "hot" like in this scenario. It would have been bad, m'kay?

After testing in multiplayer, I can confirm that SRS in fact does NOT count as a broadcast for ADF. Darn that would have been perfect. Calling JTAC is probably the next best thing for a long broadcast to use to get direction on your wingman. Telling a flight member to do a recce is also relatively long if you forget to put a JTAC in mission. I also tried using triggers to do it, but transmit message is only available as an AI task set/push and obviously we are not AIs so it didn't work. On a related note, does anyone know when the F-18 got its datalink capability in real life? We've expanded on the mini-campaign set in '89 that came with so trying to compile what tech is contemporary. May the jet gods help us when the Soviets start using 27ERs and ETs and we don't yet have AMRAAMs.

That is a good idea. Might work really well too as JTAC doesn't answer any but the first aircraft in a flight. And I wholeheartedly agree, the Tornado NEEDS to be a module one day.

I am unaware of anything that would give useful distances in CLOSE formation flying, but using Air-Air TACAN with your wingman will give you the range in nautical miles ie. 1.2, 7.6, 0.4, etc. I imagine it is also easier to judge distance for real pilots as your eyes give a better sense of distance than this sim does. That was what I was thinking too. I am going to try that next time my brother and I fly. Would be super useful before we have our datalink integrated.

I am familiar with using Air-Air TACAN to get ranging information on a wingman. Is it possible for a human controlled Hornet to broadcast an ADF signal, and for another human controlled Hornet to pick it up the way one would with a ground beacon? I imagine it is not as it seems like something I would have found in a forum or even Google search. I also pose this question to any ADF capable aircraft in the sim. I mention the Hornet specifically because I am most familiar with it.

Then that does appear to be it on the bottom, thanks. Going to be interesting to use in comparison to the Flanker/Fulcrum.

Yes that's very true and it is remarkable how that familiarity can lead to more efficiency too. I'm very fond of the VVI display on the HUD when in Nav Mode myself that the Russian jets have. I quite like the Su-25A's gauge layout as well. Can't wait to get the Flogger and see what it's like. I've been under the impression the MLA has an IRST. Is that true? And is this it?

Thanks Ghost. Hopefully ED will implement it for other flight members now that the Hornet is CAS capable.

Enjoying the new LASER Mavs for the Hornets, but as it's my first time setting up AI JTAC, I thought I might be missing something. In the attached mission file, I have 3 total JTACs set up. Each one is the lone vehicle in its group. JTAC 1 and 2 are set to FAC assign the same group. JTAC 3 assigns another group elsewhere. My brother hosts the mission and is the second aircraft in my group. Thus far he has been unable to get a response from JTAC 1 or 2, while I am able to. Does JTAC only respond to the lead aircraft in a group? In our tests he contacted JTAC 2 first while I contacted JTAC 1. When that didn't work for him, we tried switching JTACs. JTAC 2 then answered me but JTAC would not answer him. Again he is the host, and the second aircraft in my group. We do NOT attempt to contact the same JTAC at the same time. We have triple checked that he is on the right frequency and is using the radio set to that frequency. And lastly, I have not been able to get JTAC assign me targets unless I have LASER Mavs onboard (he does respond this time though). On all my tests the JTAC was set to call upon either unguided weapons, or just the auto setting. Obviously he does not assign targets when I have only guided weapons and he's set to unguided, I know it wasn't that. Hopefully someone knows what we're doing wrong. Thank you in advance. ACPW Practice Range.miz

That is a great chart to have, thanks for providing it! I've been trying to figure out how to do the math myself, what formula did you use to get your moments of inertia? I've gotta know!

You aren't giving me this free content fast enough! You should probably quite your other jobs. Trust me, I'm worth it ;) In all seriousness this module couldn't come at a better time! I have two friends getting into DCS in October-November so they'll get to learn the Grach and your fantastic Skyhawk before having to spend a penny on the sim. I've long been fond of the A-4 and am VERY excited to get my hands on it. I really appreciate the great work you're doing. Here's to November being the new Christmas! :holiday:

The problem has been solved. Windows told me my NVIDIA driver was up to date, but it lied. Using the NVIDIA website will be my method from now on. Thank you Mustang for your help and anyone else who perused my crash logs. Happy flying everyone.

From the Nvidia control panel, I set it to use the High-performance NVIDIA processor when running DCS. I also set my global settings to the same. I had the same crash. I wasn't able to find any other ways to disable it that did not involve physical action. I am also tentative to do more as everything else in DCS superbly is running superbly and I worry changing those settings might hurt that. This time I got a screenshot of the GPU related error message. Turns out it did not have the word GPU in it, only NVIDIA (why eye-witness testimony is relatively unreliable). The same error message appeared on both these attempts. I have attached the screenshot and the two error logs. I should also clarify that I can load the Caucasus Map, and loading into my brother's hosted Persian Gulf mission was quick (when it doesn't crash on load). The most consistent crashes are when attempting to get into a cockpit or spectating an airfield (both close to the ground) and I have yet to succeed in either. dcs.log-20180929-083457.zip dcs.log-20180929-083928.zip

The Metashaders Error didn't upload first try so here it is... I hope...

So I have availed myself to the free trial of the Persian Gulf map but have yet to be able to get into a cockpit there. Mission Editor works fine, set up a mission for multiplayer touring. Upon connecting the game would crash. Sent every crash log via that super handy feature. Attempted to load the mission in singleplayer and it worked BUT only until I attempted to get in a cockpit or spectate an airfield. I searched around and found suggestions to ensure my GPU is fully updated. Windows says it is. I also manually installed a number of backlogged Windows updates. This actually hurt my disk usage but I've got it under control via disabling update search feature for now. On one of the crashes, I received a little flagged message down by my start bar's clock but it disappeared before I could print screen. The message said something about my GPU, possibly timing out, but I can only guarantee the word GPU from the brief glance I got at it. Another crash gave me a error window regarding metashaders. I did click retry a number of times and came back to the same error on each try. I have attached a number of crash logs, my dxdiag and the screenshot of the metashaders error. Hoping someone can help before the free trial is over. My brother and I might be getting the map for each other for Xmas and the free trial is a great way to get us hooked... you know, in a good way. Thanks for any help in advance. I might forget to say when I'm in troubleshooting mode. dcs.log-20180929-053208.zip dcs.log-20180929-053446.zip dcs.log-20180929-061517.zip dcs.log-20180929-062106.zip dcs.log-20180929-075348.zip DxDiag.txt

Just wanted to make sure this has been reported as it didn't come up in a forum search. If you don't look behind you the sound it makes is even a little immersive haha. Track file attached below. Wing Vapors Bug.trk

1. Designate a target point via the "ball and chain" mode. 2. Switch to A/A mode. 3. Switch back to A/G, the target point cannot be normally undesignated. In order to undesignate it I must move the Sensor Control Switch to a new position, then back to Forward and hit undesignate again. When switching to A/A mode or simply an A/A weapon, the radar is forced to look down to its gimbal limits. It is possibly looking right at the target point. I also noticed that after undesignating a target point a time to release indication remains (static value), it takes two depressions of the Throttle Designator Control to first clear this indication, and then designate a new target point. And lastly and possibly unrelated, during my tests to define these conditions, I noticed my range to target point indication value (on the HUD) sometimes fluctuating with my aircraft's pitch. The target point on the HUD would also sometimes fluctuate rapidly to different spots on the HUD. All these tests were done from spawning midair though it also occurs when spawning from ground, cold. P.S. I love this module.

Haha, this happened to me too! When I first updated it wasn't enabled, then later it was. I thought I broke my throttle until I looked at the digital one in the cockpit.

I have a workaround with some functionality. 1. For the initial mounting of stores, arm with 5 different weapon types. 1 on each possible pylon. ie. screenshot 1 2. Start the jet as normal. 3. Rearm again with your desired payload (choosing from any of the 5 weapon types you used in step 1). This has allowed me re-arm hot and utilize any of those 5 previously selected weapons in sorties. After re-arming, if you had a weapon system selected on the stores page, you will have to select a different one, then re-select it AFTER the ground crew says "rearming complete" and you see the stores on the wing form diagram update. I can clarify in a private message more if anyone desires such, to keep this post from going too long... er... Happy Hornet-ing everybody!

That's better. Hypothetical: Would it be possible to fill in a previously cut mesh, then cut new "holes" for numbers after? This is assuming I have access to the mesh itself. What do you mean by primary function/focus? Just want to make it clear again, I'm not meaning for ED to do this, in case that is what you were thinking. Also Ironically, my current desktop image is an older image of CF-188745 parked at an airshow. From the picture quality I estimate circa 1980s and it DOES NOT have the serial number under the flag on the tail. So Wags doesn't know what he's talking about, we're clearly getting earlier block Hornets ;)