JTFF - Raph

+1 Here there is a conflict between DL and IFF As you can see on the picture is was surprised, rejoining the tanker and he was identify as hostile. When I IFF interrogate, there is the green circle over the red plot. Notice that half of the time you can see your own aircraft on center DL identify as hostile. (XMT was turned OFF to see if it could change something, but nothing happened)

Already reported, you have to choose the leader plane, if you pick one wingmen it will crash to desktop. They are working hard and trying to patch it ASAP https://forums.eagle.ru/showthread.php?t=258275

Hi, the strobe light with 4 sequences is very usefull for formation flying (see who's number 1, 2, 3 or 4) but is not visible by other clients. 100% reproducible with a quick online flight. I can send one track when I'll fly with my wingmens.

Full .zip dcs.log-20191218-204323.zip

when you select the leader of a group it works but another wingmen slot will instant crash. LOG CRASH.txt

Now with Datalink + Flood lights my 100 FPS drops to 1-3 per second so I cannot fly by night with. It's worst than it begun, when I was closing SA I was recovering perfs, now it is not working so it's unflyable :/

Hi, there is an issue on 3 positions switch. (Aknowledged) Especially for the alt/att autopilot switch, on the warthog you need to make a double input to set it up or down, travelling by the neutral position. There is a missing lua line for this issue but in this track you can notice one thing: when the A/C is over 45 degrees of turn the 3 positions switch is working poperly, following warthog's switch. Sorry for my bad english I hope this thread will be easy to understand. Regards. Warthog input issue.trk

Hi! Do you guys have any news about this one?

One more track with a couple of tests on Nalchik, elevation 1411 ft QNH 29.92 default. Hot start on parking: - HUD isn't matching with the elec/pneu alimeter - To reach 1411 ft I need to change alti to 29.99 Cold start on parking: - HUD isn't matching with the elec/pneu alimeter - to reach 1411 ft, 30.01 is needed with pneumatic - to reach 1411 ft, 29.94 is needed with electric The HUD is displaying 1400 every time and not displaying another value when you change altimeter settings Note that sometimes on other airbaises with other conditions you need to change brutally the altimeter to reach the correct QNH, this test was very soft. Altimeter issue.trk

Here is a SP track, logs and two more screenshots Conflicting shadows and perf loss.trk Logs: (invalid file on upload don't know why... it's a txt) 2019-11-30 16:39:12.951 INFO DCS: options.graphics = { ['messagesFontScale'] = 1; ['rainDroplets'] = true; ['LensEffects'] = 3; ['heatBlr'] = 2; ['anisotropy'] = 4; ['water'] = 2; ['motionBlur'] = 0; ['outputGamma'] = 2.5; ['treesVisibility'] = 10000; ['aspect'] = 1.7777777777778; ['lights'] = 2; ['shadows'] = 4; ['MSAA'] = 2; ['SSAA'] = 0; ['civTraffic'] = ''; ['clutterMaxDistance'] = 1500; ['cockpitGI'] = 1; ['terrainTextures'] = 'max'; ['multiMonitorSetup'] = '1camera'; ['shadowTree'] = false; ['chimneySmokeDensity'] = 10; ['fullScreen'] = false; ['DOF'] = 0; ['clouds'] = 1; ['flatTerrainShadows'] = 2; ['forestDistanceFactor'] = 1; ['width'] = 2560; ['visibRange'] = 'Ultra'; ['effects'] = 3; ['SSAO'] = 0; ['useDeferredShading'] = 1; ['sync'] = false; ['textures'] = 2; ['scaleGui'] = true; ['preloadRadius'] = 150000; ['height'] = 1440; ['terrainMapMFD'] = { ['distance'] = { ['mapLodDistance3'] = 200000; ['mapLodDistance2'] = 100000; ['mapLodDistance0'] = 25000; ['mapLodDistance1'] = 50000; }; }; };

Hi there, There is a conflict between consoles and instrument flood lights. It's maybe one of the causes of performance loss in the other thread (FPS drop with flood lights) Notice that this thread has still the status "can't reproduce" but there is a 20-25% of FPS loss for most of the users. Should be a verified issue now I think Here is a screenshot of the cockpit glitch, it makes black squares spinning all arround the consoles: [ATTACH]222026[/ATTACH]

Oops sorry I did a mistake, I think with the link of this thread in the message! I'll create this one in another :) edit: this one now https://forums.eagle.ru/showthread.php?p=4122362#post4122362

+++1 Same since the first release, i thought this bug was known and reported?! The HUD displays wrong informations and Altimeter seems to be incorrect to (QNH or QFE is not matching with VAC cards and weather most of times).

Here is the new crash log with the autoexec used! dcs.log-20191129-161402.zip

wilco

Hello, I have an issue with the voice chat: I can choose a driver for "Main audio out" or "Headphones" but there is nothing in the two lists "Voice Chat output" and "Voice Chat input". My drivers are up to date. Be advise this thing causes instant crash of DCS if you are trying to join a server with voice chat activated. So you must unactive the voice chat in your settings to join correctly the server. (repair done and client isn't modded) here is some screenshots and logs: dcs.log-20191128-150028.zip Best regards.

+ 1 we were speaking about this subject with Nineline if I remember correctly! This issue is not present just on the F-16C. I hope they founded the issue.

Ok on the ressources monitor I see CPU and Drive hight value of usage. I can't see anything about the GPU because the device is used at 100% every time. Flood lights activation is in the red square

You are wasting your time please don't leave comments without a track or anything else that can help ED

So if you are in A/G mode with the missile mode layered "in background" because you forgot it you'll fire a missile when you pickle? That's dangerous :O

SP: - Hot start parking : working - Hot start in flight: working - Cold start parking: not working MP: - cold start: issue isn't present on every server, perhaps depending of MOOSE/CTLD/MIST scripting? Video from another user: https://www.youtube.com/watch?v=oFOm3VYn__A&feature=youtu.be

Same issue I need to place the bore on the target and quit/reactive the boresight mode 2 or 3 times to get the lock

Here it is SP short track, but this time the vertical symbology was moving, not the TGP sensor cue. Most of the time nothing is moving, cue at the center of HUD, vertical line for release point stuck on the right side of HUD. CCRP freeze + TACAN M-SEL F-16C.trk This is not the subject in this thread but you can use this track to see the TACAN band broken, I think because M-SEL ("0") is not supposed to write the number 0 in tacan character chain.

Since the INS implentation we have got all the CCRP symbology freeze while you are moving the TGP. Track attached. I don't know if the issue is still reported but I didn't find anything on it. Feel free to delete my thread if it's the case. This is a MP track so I used wetransfer (60mb). Cold start, Takeoff, Issue tests, Landing. https://we.tl/t-lXHvkfZsLF

+1 In MP not on the Viper especially you will see tracers on other aircrafts when they have no tracers equiped on board.