Saruman

+1 This same thing happened to a friend of mine (to me it happens in MFD, instead, there's huge mosaic on the right)

I know about the ghosting problem with MT. In my case, there's also an artifact problem though (see attached image, on the right, all those coloured lines). null

I think it would be nice if, for every module, we had some short clips running in background in main menu, starring the theme module, instead of the still images we have at the moment.

At the moment, when you spawn in cockpit, you find that the aircraft imported automatically up to 50 non-hidden anti-air threats in the COORD page, taking them from the ones present in Mission Editor. Now, it could seem a feature, but it's clearly a bug, because on very large mission (like the ones running on more famous public servers) you have a lot of mess with those auto-imported threat points, while all you would like is an aircraft in a clean state. Auto-import of threats from Mission Editor should be therefore disabled or, at least, changed to an opt-in/opt-out system, letting mission designers and/or players to choose whether they want to use it.

Can't check right now but irrelevant. It's a gpu-less headless dedicated VPS server running smooth until updated to 2.8. It's not a desktop. 2.8 is clearly the problem. EDIT: I tried to remove Awacs from my complex running mission on the server, just out of curiosity. CPU usage went consistently down. I guess Awacs is doing something weird in new release under the hood? Inviato dal mio BLA-L29 utilizzando Tapatalk

As per thread object, 2.8 performance on a gpu-less dedicated server VPS is horrible, CPU is always throttling between 80%-100% regardless of number of clients connected, with intuitive consequences on lag/freezes (like Awacs or tankers being still in the air). On 2.7 CPU was very low on usage and server was pretty smooth. No mods of course. Inviato dal mio BLA-L29 utilizzando Tapatalk

Confirmed. Serious bug, it breaks a lot of complex missions that rely on looping route Inviato dal mio BLA-L29 utilizzando Tapatalk

It should be false by default, as stated in the changelog Inviato dal mio BLA-L29 utilizzando Tapatalk

Number 3 is happening since a long time on busy servers, Awacs is so dumb that he calls contacts at 300 nautical miles. ATC/Awacs should have been top priority rather than rainbows and ice halo... Inviato dal mio BLA-L29 utilizzando Tapatalk

As per thread title, I find that KC-135's refuelling lights on tanker's belly are too dim to be clearly looked at. Could ED make them brighter or implement an on-screen display like the one you have on Supercarrier for IFLOLS?

+1. Moreover, AWACS makes callouts for contacts 300 mn far away. It shouldn't. Besides, at least since latest update, AWACS makes double or triple overlapping callouts (to your group and other groups) for the same contact. That's another thing it shouldn't happen (at least make him tell "all stations").

It does not break anything if you use different LUAs for different aircraft frameworks. Yes, you have to restart when you select a different LUA to use in settings page, but it's a minor issue. For example, I use one LUA for F16/A10/F18 (they all share LEFT_MFCD and RIGHT_MFCD), one LUA for F14 and one LUA for AH64D. And for AH64D I only had to change last line of aforementioned files. But I cannot now fly in multiplayer servers, not being able to pass integrity check. That's why team should officially modify those two lines.

Sorry to up this, but after 3 months it's still an issue. It really can be solved by the team only changing last line of MFD_plt_left_init.lua and MFD_plt_right_init.lua, by replacing "LEFT_MFCD" and "RIGHT_MFCD" with something else like "PLT_LEFT_MFCD" and "PLT_RIGHT_MFCD". I can see team busy on a lot of other things, but it's truely a very quick modification...

Yes. I would like to know it too. Same problem with FLIR. Admittedly, it's more realistic but, at night, it's a lotta more difficult to find spawned vehicles with engine off and cold.

Please, ED, since available theaters are becoming a considerable number and therefore dedicated server now requires quite a large storage, make server admins choose which specific theaters they want to install on their server, without forcing to install all the theaters at once.

Hi, I was looking forward to rotate DCS logfile after it reaches a certain size. Is there any option to achieve this? Dedicated server, by the way.

Since latest update, if you have multiple units (tankers, JTAC, etc.) sharing same callsign but different numbering (for example, "Uzi 7-1", "Uzi 8-1", etc.), comms menu shows them with same callsign and same numbering. Until latest update, comms menu showed the correct callsign and numbering. null

If you limit carrier resources and you make AI planes takeoff with a certain loadout, carrier resources are not diminished of the corresponding loadout. Besides, you can select carrier as supplier for airbases' warehouses, but airbases' warehouses never receive anything from carrier (you always see E0 in the resources tab of airbases which should be supplied by carrier).

CPG and Pilot share same LEFT_MFCD and RIGHT_MFCD ids for monitors and CPG id always overwrite the pilot one, regardless of the seat the player chose. To export pilot monitor, player therefore needs to modify .lua files under the AH64 mod folder, which breaks integrity check for multiplayer. ED should give different ids to monitor (it's a 5 minute bugfix) and/or leave the default ids but let player export the monitor for the chosen seat.

If you name one unit something like "Primary destroyed John Doe" or "Secondary destroyed John Doe", and you save the group, which the unit belongs to, in a static template, when you reload the same static template the unit name is simply "John Doe", even if the corresponding STM, if opened in Notepad++, retains the full name of the unit.

You configured it correctly. Too bad it didn't solve in your case.

Nobody else in my VFW had the problem (including myself) except the only guy, among us, using Ryzen 9 (like QuiGon's friend with the same issue). My friend had the issue with our mission and with Blueflag's (Buddyspike) one, not on other multiplayer missions. This is why I started thinking which common element our internal mission and the Blueflag's one have, and whole warehousing thing (that is, with resupply logistics chain) seemed to me the appropriate answer. Disabled it and my friend can now play at good FPS. His log was originally full of errors, the same errors that are in the log of QuiGon's friend (posted above in this same thread) and that are absent in my own logfile. In particular, my attention fell on the following errors from my friend's logfile: 2022-03-21 16:20:55.982 ERROR EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH 2022-03-21 16:20:55.983 ERROR EDOBJECTS: Destruction shape not found GAZ-66_P_1 2022-03-21 16:20:55.983 ERROR EDOBJECTS: Destruction shape not found KAMAZ-FIRE_P_1 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object DURANDAL with id=62 already declared in table BombTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object AV8BNA_AERO1D_EMPTY with id=299 already declared in table ContainerTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object M2KC_02_RPL541_EMPTY with id=603 already declared in table ContainerTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object M2KC_08_RPL541_EMPTY with id=604 already declared in table ContainerTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object M2KC_RPL_522_EMPTY with id=605 already declared in table ContainerTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object AIM-9 with id=22 already declared in table MissileTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object AIM-9P with id=135 already declared in table MissileTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object AIM-9X with id=136 already declared in table MissileTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object AIM_7 with id=21 already declared in table MissileTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object HB_F14_EXT_PHX_ALU with id=320 already declared in table MissileTable 2022-03-21 16:20:55.985 ERROR EDOBJECTS: Object X-59M with id=54 already declared in table MissileTable Now, I don't obviously know the source code by ED, but that smells to me like ContainerTable and MissileTable are tables having to do with with stock in warehouses.

It's not simply the limited ammo. It's the re-supply system used by ED for warehouses with limited supply. As you know, you can configure warehouses with limited ammos and you can decide that those warehouses: i) must check for their stock every n minutes, ii) must ask for replenishment when a certain treshold is reached, and iii) that the replenishment must reach the warehouse at a given speed by predefined other warehouses of your choice. Our internal mission, as the Blueflag one, uses this whole complex system by ED, that is, not only the limited ammo, but the whole re-supply chain logistics. Well, I disabled it and my friend can now fly at full FPS! If I re-enable this whole warehouse system by ED, my friend comes back at 3-4 FPS. In the meanwhile, I made him set his preload radius to the maximum value. Now, in the forecoming hours, I'll enable again the whole resupply chain logistics on one base to see if the problem depended on preload radius or on the logistics by ED. Should it come out it depends on logistics system by ED, I'm going to open a new thread reporting the thing to ED, because, in that case, something's going on on their side, especially for Ryzen 9. The thing that only a very few people is reporting this, also on Blueflag Discord, must depend on the fact that only a small, small bunch of missions implement the whole resuplly thing by ED. 99% of missions set unlimited ammos and therefore no resupply system.

UPDATE: Even the friend of mine has a Ryzen 9. I suspect something's going on with Ryzen 9 and some missions after latest update. My friend has problems with Blueflag mission and with our own mission. If I'm not wrong, the only thing our mission and Blueflag's one has in common is that they use warehouse system by ED with limited ammos and active suppliers. I guess ED could investigate if last update brought some problems between Ryzen 9 and ED's warehouse system when the mission uses limited ammos and suppliers warehouses.

I dunno which CPU my friend has, but it has 12 cores from dcs.log. Then 64 GB Ram and a 1080 TI. You know what? I compared your friend's dcs.log with my friend's dcs.log and they have the same exact ERROR reported in their logfiles. My own log, instead, does not have those multiple errors.