Saruman

Nice thanks, Flappie. I'm curious. Do you know if it happens because of some graphic settings or only on certain videocards? Because a friend of mine does not have it (he's on Nvidia, I'm on AMD).

1) MT, I did not try ST. 2) No mods installed at all, I never use them 3) Yes, fresh fxo and metashaders

Hello, since latest update, flying during night, it seems light sources create some problems. This is how I see the light coming from a ship near the carrier. Same problem when flying above random urban cities, if I look towards them. Syria map, by the way. null

Cold and dark on carrier, carrier doing its own straight route, ground crew screaming "Hey what are you doing" all the time, at random, when you request rearm and refuel with airplane still off. Now, I'm happy about all announcements in "2024 and Beyond", wonderful, I love you and your efforts and will continue to support them, but could you address core's fundamental issues first of all? Let me say this one does not seem too difficult to solve, I don't know DCS' code of course but I know coding and it would require perhaps a couple minutes to tell DCS to consider F18 cold and dark stick and literally glued to carrier to avoid it. Please, do not ask me for tracks. You know problem is there, you just have to put one carrier and one F18 in a clear day with a bit of windgust and ask ground crew to rearm and refuel,. This issue exist since years, yet it's not solved. And it has consequences, because if you take off ignoring all the "Hey, what are doing" screams by ground crew, your weapons are probably unwilling to detach from pylons when needed, so....

I can confirm, I found this thread while looking if someone had this same problem. I was flying F18 and exporting AMPCD to second monitor. It only happens during night missions and, for me, only since latest update. Flickering is not terrible or continous and not very noticeable in my case, it seems like a quick monitor refresh every 40-50 seconds and only on the second monitor (the one I usually export MFD to).

Yes, I watched the videos thanks, and I'm doubtful whether I should add Awacs to donors on mission editor for every flight. It seems like it flashes on SA/HSD page of I don't do that? Inviato dal mio BLA-L29 utilizzando Tapatalk

About new datalink features: do we need to add Awacs as donor in mission editor for any group or will Awacs be added as donor in any case?

@Braunn In my case 7900XTX does not become really hot because I don't use Zero RPM and I set fan curve, so junction hottest temp in DCS is around 60 degrees, but as I said I'm CPU bound (old Intel 6700k) and I have an old 1080p 60hz monitor, so GPU workload is low anyway. I use Radeon Chill to have between 100 and 120 FPS because I can reach over 200 fps in DCS and therefore fan noise from GPU can get a bit annoying. You know, I went for the Sapphire Pulse, because the Nitro+ costed too much more (+150 euros), and fans on Pulse are a bit noisy if they spin over 1800 RPM (at maximum 3200 RPM they are a proper tiny jet). Back to the matter of the topic, I tried TAA but it's disappointing, whether you use it with FSR or not. Too blurry aliasing and tons of ghosting. If you really need extra FPS and have a compatible GPU, you could take some risk and try the new frame generation tech provided by latest preview drivers from AMD (you could enable it in all games, even the ones that do not support FSR). P.S.: I know 7900XTX is overpowered for my current build. I'm going to upgrade rest of my rig in a few months of course, I bought 7900XTX because I had a 10-years-old Nvidia 970 and decided to start upgrading by changing GPU first of all. Inviato dal mio BLA-L29 utilizzando Tapatalk

Because flight could belong to a public server with tons of F16/F18. Inviato dal mio BLA-L29 utilizzando Tapatalk

But the fact that DCS would not generate a kill event at all is not. It's relevant for scripting, whether you use DCS' own SSE or any other scripting framework.

Don't name Moose or they will never fix it, but will take shelter into the usual "We do not support external mods/scripts"...

As per object, TAA + FSR draws only half of my main screen (I have 2 monitor, the main one and a little 10'' one I use to export one MFD) Cockpit bar, in the lower part of monitor, is correctly drawn for all the monitor size though (see second image). EDIT: Just to be clear, it only happens in 3D. Main menu and mission editor are ok, before you enter pit. null

No problem here with 7900XTX, but I do not use FSR (I dislike upscaling). FPS went even higher on their own, though I set all on high/ultra and max values. But GPU load went higher too (from usual 35% up to 70%, I am CPU bound). I'm on latest stable driver and no AMD's tech enabled besides Radeon Chill (to limit FPS to 120 to make GPU stay more cool, I have a poor monitor) Inviato dal mio BLA-L29 utilizzando Tapatalk

After latest update, I self-killed twice when 120C left the rail. I might be doing something very stupid, but I am not maneuveuring in A/A in a different way I used to before latest patch. Missile leaves the rail, lofts in front of the plane then it does not gain speed and you overtake it at 1.10 Mach. It should accelerate a lot faster, otherwise you could not fire it while supersonic. Attaching last tacview file. Tacview-20230903-140102.acmi

Still an issue. If clients are bugged (usually, the first client taking a slot on dedicated server), in MP tankers are all 1-1... If you leave, and reconnect, radio comms are ok, but callsigns on F10 map are not.

I oversimplified the example code, because the real function loads inventories from a file, since I created a persistency system to use through rotation of missions being part of my campaign (three missions rotating, one for each time of the day). There is also a resupply system every n days in real-world time, but it's irrelevant to my question. ED can change weapon codes, first of all. Second, new modules and new weapons will be added and it would become a second job to add, check and update a custom weapon table with only the items of interest (consider I run a 24/7 campaign, so new modules will always get added). I started with a (long) custom table, changed my mind on the fly after the above considerations. Third, many items have the same name though being distinct (for example "Fuel tank 300gal" for F14 and F16: the F16 version has no code, the F14 has it). To sum it up: inventory hardcoded by ED is a mess (did you ever notice some items only displaying "!!!!" ?). Last but not least, last time I trusted ED not to change anything fundamental, they changed the IDs of all buildings in Syria, which I am referring to in some mission files (DCT template definitions used by the underlying DCT framework used by campaign), so I had to double check all the new IDs and modify accordingly the mission files. About performance, real script runs great, thanks, one time at init and one time before rotating to save updated warehouses into a file. I already make the real code called by timer.scheduleFunction() and delay is 60 seconds, more than sufficient to load every unit I guess, since I can spawn on the carrier 1 second after mission starts. As far as I can read and understand the code, it's all that matters. Script is not GPL-ed and have no contributor, therefore I'm the only one who will ever mantain it. That said, I'd prefer not to derail from argument, which is: carriers do not always get updated by setting items in the aforementioned context; no issue with common airbases instead. Anyone experienced/tried that?

After testing a bit, I noticed that carriers do not always get updated after setting items, at least in my mission. Some times they get updated, some times (when restarting same mission) they do not. Here's a sample oversimplified code local friendlyAirbases = coalition.getAirbases(coalition.side.BLUE) for i = 1, #friendlyAirbases do local w = friendlyAirbases[i]:getWarehouse() local inventory = w:getInventory().weapon for wpn, _ in pairs(inventory) do w:setItem(wpn, 30) end end Common airbases always work fine instead.

What about ammos sharing same name? For example, looking at inventory, you have two distinct "Fuel Tank 300 gal": one is for F-16, the other one is certainly for F-14. How can you refer to one or the other, considering that the F-16's droptank seems not to have an unique typename (the F-14's one is weapons.droptanks.HB_F14_EXT_DROPTANK)?

Does it work for carriers' warehouses, too?

Hi Flappie, thanks for asking. The mission I noticed the bug was a dynamic one of mine, so it's not shareable because you would need also all scripts and underlying framework. Anyway, it seems the problem solved on its own amongst last updates since April, so I guess we can close the thread. Regards Inviato dal mio BLA-L29 utilizzando Tapatalk

970 here Inviato dal mio BLA-L29 utilizzando Tapatalk

I don't think you need a third screen. I'm playing with shadows off since I had the problem and it runs fine without shadows and multisampling filters. Inviato dal mio BLA-L29 utilizzando Tapatalk

Yeah, attach the monitor and set it up in Windows on the left side of main monitor (or on top of it; if you set it on the right, no midline appears). Here's my setup, for example: In my case, monitor 1 is 10'' and 1024x768 resolution, monitor 2 is main 26'' monitor and 1920x1080 resolution. Windows decides the numbers in an awkward way and you can't change them, so don't bother if your second monitor is listed as number 1. Then, you must create a .lua file (name it at your wish) in %USERPROFILE%\Saved Games\DCS.openbeta\Config\MonitorSetup folder (you have to create the latter folder, if not already existing) and you must setup the viewports. For the purpose, do consider that x and y axes start from top-left of monitor 1 (based on my setup, ymmv). So, for example, in my setup, first pixel at top-left of monitor 1 has coordinates x=0 and y=0. Taking this into consideration, you have to edit the aforementioned lua file by writing into it monitor resolutions, corresponding coordinates and viewports you want to export on second monitor. I'm attaching my lua file, to let you easily understand it and adapt to your needs and personal setup. Saruman.lua After all of this, you run DCS, go into settings, open "Monitors" drop-down menu and choose the lua file you edited(figure attached). Restart DCS and you're good to go.

Bump. Any official statement about this? It happens after latest update too. Inviato dal mio BLA-L29 utilizzando Tapatalk

*toc toc* +1