toutenglisse

Just had the case today - Bignewy told me to delete old ones to make room : go to your profile page, click on attachments (left side Bottom line), click on last page (oldest) then click on checkbox on upper right corner and click "delete" to delete the whole page of attachments. do again for some of last pages until you think room is sufficient.

I noticed since last update (but I don't know if related) that F18 wingman missed target with HARMS in certain condition (high but not far from target). Here I reproduced : placed a F18 AI at the limit where bug happens : sufficiently high and close to target (20K feet / a bit more than 20 km away). The first HARM interrupt the loft soon enough to intercept target, but second one, due to loft, fly over the target. AGM88c-loft-bug.trk

I've not tried since latest OB hotfix patch, but in these conditions Hornet AI usually bugs on kc135 mprs, and Viper AI bugs on kc135 (good hose visual connection for Viper but takes no fuel untill "2, rejoin...bingo fuel...eject" in a minute). But sometimes it works...

tack så mycket ! for valuable and fun tool.

If easy comm menu get totally unaccessible, then you can't ask any help to ground crew with a dark/damaged aircraft (refuel, repair, ground power elec/air pressure…).

High probability that it's related to your ram being maxedout. Also your last logical core seems very high (even with low reso/refresh-rate of tasks manager monitoring). If at idle in windows you have no cpu usage (0% + some little spikes) then it's ok on this side. (but with 1 logical core near maxout in DCS, you could probably see benefit from turning hyperThreading off) I've also seen high memory usage these times, but I still have room with 32gb. It's probably your culprit ?

Take a look at each cpu cores loads, while playing but also at idle. I've had two sources of embarrassing/parasite cpu loads : 1st is ok and happens sometimes but not long, it's windows anti-malware running 30% cpu during less than a minute. Not a problem. 2nd was an issue, it was "system" process taking all the time at least 30% cpu usage. I had to do a proper cleanup/optimization of ssd c: using windows tool, to get rid of it. When I had this issue it was impacting fps/stutters on DCS(vr), because cpu usage was much higher than usual (usually over 50% on all cores, but with issue it was near 100%).

I said that because your wish is on Hornet's thread / wingman fuel state...

D/Link on, SA page with cursor on wingman symbol gives reading of his remaining fuel amount.

No issue with MS Sidewinder FFB2 and A10C, but his joystick has vibrations, not FFB.

I tried also and it seems obvious that in this mission the Game mode or Game controls is enforced. (hard coded in the mission)

The 3 Tgp (A10-F16-F18 ) are also working ok in Bhot/Whot modes on my side actually (but I had the bug before). What is different from before on my side is that I'm not able to break it again by changing options (before, just changing chimney smoke to other than zero, or changing AA would break Flir but now I'm unable). I use latest NV driver (445.87) installed with prior cleanup of previous driver, BUT I've also done something new that maybe you can try, Nealius and others, if your Flir is still broken : I've deleted Directx Shader Cache using windows Admin Tools / Disk Cleanup / C: / and tick if not already ticked directx shader cache. Just in case there is a relation - IDK for sure and what "seems" to works for one have random chances to work for another…

Left Alt + Z (or W on AZERTY keyboard) put sim time speed in halfrate - that's what you have activated in your video. Normal speed is Left Shift + Z

You can try : go to command settings, A10c sim, axis - delete your joystick axis and rebind them. Others solved intempestive button issue this way. (it may well be different than resetting to default?)

Page 139 of DCS Hornet flight manual : "The AUTO mode provides computed, automatic release of bombs. It computes release solutions for dive, dive toss, level, and low angle lofts up to 45 degrees. "

https://forums.eagle.ru/showpost.php?p=4284735&postcount=8

I was playing this user's mission : https://www.digitalcombatsimulator.com/en/files/3308344/ I started with Huey, destroyed 4 vehicles then RTB, and choosed a F86F client slot. I destroyed 2 APCs with rockets and 2 Tu95 guns-missile and on the way back to Kobuleti the sound suddenly stopped playing. I pressed menu button on my Oculus remote that swapped rendering from DCS to Oculus home and immediately heard the home's music, so my headphones were OK, then back to DCS pressing again the button, still no sound (game unpaused) in the F86. I made this report, but shortly after I saw this thread : https://forums.eagle.ru/showthread.php?p=4313403#post4313403 So maybe it's the issue reported in this thread that I experienced ? I noticed in my log that audio channel used by DCS is channel 2, so no driver error like others had with channel 0 used by DCS.

You can use 7zip, add file to archive, and select divide in volumes, entering less than 5,000,000 bytes and ok. Your will have 4 compressed file that you can post using 2 posts (3 max files per post).

It just needs a track showing the issue because it's a rare one. Without, nothing can help. FWIW (I have no track) it happened once to me with the Hornet maybe 1 week or 2 ago but I didn't saved the long track (I should have because it's not repoducible). Same as you LGB lost track (I watched departure with F6 - tracking laser, then in cockpit view waited on tgp the impact that didn't happened, and saw impact far from target, my altitude/range and attitude TGP/target were ok, next bomb was ok). Same also happened recently (once only also) with Vikr/Shkval and Ka50 - A Vikr started tracking laser then lost it and felt down. Was too early for burning laser possible and the next ones tracked OK. Different but in a way similar sometimes out of the blue (rare) a gps bomb completely miss by far. For all it requires a track file.

Yes noticed - An ED team member said in a late patch note (not latest but just before) that this prop rendering has been reduced for the 190A8 for sake of performance and it's the exact same thing you see with the Spitfire : "Geometry of propeller edited in 2-4 LODs for better FPS performance" (I also see it but only have Spitfire since the free trial so I can't tell for what changed). So it's very possible that the change has been applied to all WWII modules except Mustang. I saw effectively with the A8 performances are a hair better but it didn't improve anything about ASW artefacts caused by propeller.

I've several times had the issue you describe in post#13, and some times (only for now seen playing WWII on Normandy) WM don't form with player but RTB. Once (some minutes ago) I launched the mission as squad leader against bombers+fighters, but launched it close to the ground : some WM directly crashed on the ground and the remaining ones (3) directly RTB. Just a thought, maybe instead of assigning a target group you can assign a task (CAP) like this way : ["tasks"] = { [1] = { ["number"] = 1, ["auto"] = true, ["id"] = "EngageTargets", ["enabled"] = true, ["key"] = "CAP", ["params"] = { ["targetTypes"] = { [1] = "Air", }, ["priority"] = 0, }, }, }, so they engage any aircraft enemy they detect ?

Related to these Navy "ufo" (I still have an issue with "object") videos, what buggled me was, last year when videos were largely released, the reaction/comments of a french fighter pilot, Jack Krine ( http://translate.google.com/translate?sl=fr&tl=en&u=https%3A%2F%2Ffr.wikipedia.org%2Fwiki%2FJack_Krine ), that had an "ufo" close encounter while training with wingman in Mirage III. He was commenting them during a radio show, and was very suspicious, doubting about almost everything (Navy source, actual original SuperHornet Flir footage, etc...). He even said during the radio show that he was unpleasantly surprised that people tand to believe him about his own "ufo" experience and ralaying his story. (He talked in detail about it in a french TV show, with other former military pilots) (his experience : "ufo" played with his flight at several times, chasing - being chased and always screwing away accelerating in the blink of an eye. Close visual contact, no ground radar contact - no radar of course on Mirage III). So I largely understand why what usually rule minds are still things like Fermi paradox ( https://en.wikipedia.org/wiki/Fermi_paradox ). But no rant about it. It is how it is.

Dcs.txt joined. I exited DCS when the sound stopped playing. EDIT : sorry I just seen "sound stopping bug" reported in F86 thread. Probably same issue. dcs.zip

https://forums.eagle.ru/showthread.php?t=266190 https://forums.eagle.ru/showthread.php?t=269441

Hi Pike. This is where I aim with Gbu38 in TOO mode + A-track to get the best results (lowest central visible point of target). If I use P-track I get relatively bad results. Note in this video the conditions are optimum (no wind/turbulence, tank platoon is set to not disperse under fire and shows rear aspect). It's not always a direct hit but if not, it at least deals damage.