diditopgun

Hello ! In the HB F-14 manual, special weapon ADM-141 TALD is listed. Will it be available at EA release ? How will it work ?

:shocking::surprise::worthy: I have to clone myself to be both in front and back seat !!!

Yes Mk20/CBU-99 are weak from the beginning of the EA... Here is two tests of 4x CBU-99 on soft and light armored targets. Visually the effect area is wide and everything inside should be destroyed or heavily damaged. But the result is not as good as expected and it need 4 bombs, imagine with only one bomb... Currently Mk20/CBU-99 looks more like a make-up Mk-82... 4xCBU-99 over Ural-375: 4xCBU-99 over BTR-80: Track files attached. CBU-99 Ural-375.trk CBU-99 BTR-80.trk

You're right, after some talking on an other forum about it, yes missiles should not really be affected by chaffs in most situation, but fire control radar (FCR) yes. So actually it's better about missiles (chaffs are not treat like flares), but it doesn't deceive FCR too. Chaffs are fully useless at this time in DCS...

Hi ! Yesterday a friend and I did many BVR tests in 1vs1 to test chaffs effectiveness. (Tacview used to check results) We used AIM-120C, Super 530D and R-27ER. We never succeeded to deceive a missile in chaffs. Does something has been change or broken about chaffs ? Did other players noticed this too ? Hard to prove something about chaffs but previously it was easy to see by Tacview missiles going straight to chaffs. AIM-120 looks like much more effective than before too.

Finally ! :cheer3nc:

Up ! I ask myself the same question.

AIM-7MH still tracking after launcher death. Hi ! Tonight, Last DCS 2.5.4.26552 Open Beta. AIM-7MH still tracking and killing my target after my plane being shot down. I attached the tacview. Last two engagements Hornet vs Mirage: Hornet (DidiTopGun) +00:44:15 Hornet (DidiTopGun) +00:48:43 Looks like my radar is still tracking after my death. Tacview-20190123-214120-DCS-TOPGUN.txt.acmi.zip

Yes but it's in the RIO station... XD

Hi ! My friend who will be my RIO like do stupid things to troll me. He already threaten me to jettisson canopy or eject myself if I bother him (what I like to do of course ^^). :helpsmilie: :P So, will there be an option to inhibit canopy and ejection control from one or the other crew station ? :D

https://forums.eagle.ru/showthread.php?p=3768123#post3768123 ;)

If your velocity vector go under the Pull-Up cue (horizontal bracket), Breakaway-X and DUD is display. It means your bomb won't be armed because you are too low and it won't explode to protect you from shrapnels. That was not the case before last patch, but now it works as intended. Maybe snakeyes pull-up cue is not good at this time and work as if it's a standard Mk-82. I don't know, I haven't test it yet.

You have the same crashes we have reported already in this topic: https://forums.eagle.ru/showthread.php?t=227429&page=9 Actually, no solution… :(

DCS 2.5.4.26368 has not resolved the problem. I was testing new HARM missile on PG with SA-15 and SA-11 sites. I did several tests, quit and play again, using time acceleration several time during 50min; and then a last time accélération made me CTD... Something strangle somewhere :dunno:

Sadly it does not fix it, at least in my F11 view test. Maybe it fixes it if I play normally without stressing the game, but I will have to fly one or more full missions to know it. How I set up my pagefile: This is correct ?

Ok I will try it. But I had no issue before this patch since I built up my new computer last summer. Maybe pagefile can help but something happened between 2.5.3 and 2.3.4.

I just come back from a new test procedure to reproduce the crash quickly. First I cleaned my "saved game" folder except graphic options and input, and then did a repair of my DCS. No mods installed for the tests. My procedure is to create a new mission in ME, don't edit anything, only go clic on fly mission. Then I cycle the F11 view quickly to overload terrain loading and make the game CTD. It crashed as intended several times without crash report message. Then I saw that a Nvidia graphic driver update is available. I decided to update it, but by using the fresh full install option to have something fresh and clean about it. Then I started a new series of 8 tests with the same F11 view procedure as before. That on both Persian Gulf map (PG) and Caucasus map (CC). CR=crash report message and log+track+crash+dxdiag+dmp files CTD=crash to desktop #1 PG -> CR -> CTD -> PG1.dcs.log-20190115-174603.zip #2 PG -> No CR only dcs.log -> PG.dcs.log.zip #3 PG -> CR at mission loading… -> CTD -> PG2.dcs.log-20190115-175442.zip #4 PG -> CR -> CTD -> PG3.dcs.log-20190115-175943.zip #5 CC -> CTD -> No CR only dcs.log #6 CC -> CTD -> No CR only dcs.log -> CC1.dcs.log.zip #7 CC -> CTD -> No CR only dcs.log #8 CC -> CTD -> No CR only dcs.log -> CC2.dcs.log.zip To make PG crash it's easy, only need a quick F11 cycling because terrain loading is heavy. To make CC crash it's harder, I have to spam very quickly F11 or F11+F10 because terrain loading is far more light than PG. So I think it looks like something related with memory loading during the flight, and at some point reach a maximum for an unknown reason and make the game crash. Or something like that. What is sure, is that I got only few CTD on Caucasus because the map is lighter (last weekend, 8 MP flights with a friend, only one crash). Persian Gulf map is too heavy and crash rate is high so I haven't played on it since last patch. I hope it can help. If you have more test suggestions, I'm open. PG1.dcs.log-20190115-174603.zip PG2.dcs.log-20190115-175442.zip PG3.dcs.log-20190115-175943.zip PG.dcs.log.zip CC1.dcs.log.zip CC2.dcs.log.zip

Arf… :( Yes I included my dcs.log from PG crash posts #33 #35 #44 #66 of this topic.

:cheer3nc::cheer3nc::cheer3nc: