fnslayeroc

Update: I flashed my bios and left default settings, still have them. AMD SAM and XMP now off, wont go away. i dont see shadows like this in other peoples videos. If i reinstall windows, AND DCS, to find it still is happening im not going to be happy..... there is another person having the same issue....

Here is another log that doesnt fail the integrity check, i was messing with shadows and taa to make that go away to no avail. Still happens. dcs.log

I have an AMD build. Asrock b550 7700xt 5800x3d Shadows look terrible, If i set them to low, they shimmer all over the place with jagged edges, and I get massive light artifacts. As I set them higher, the Shadows look better, but then I get really fast moving light artifacts around the cockpit, and the shadows under small edges around the hud/ufc in my f-18, look jagged. I tried forcing the options to have ultra shadows, this makes the artifacts even smaller, but they move even faster.... I dont get it, i tried turning on and off multiple settings, SSS SSAO Secondary Shadows Global Cockpit Illumination MSAA off, x2, and x4, even forced it to x8 to see what happened in Adrenaline, tried messing with AA settings it doesnt do anything at all. tessellation at 16x and application drivers. 24.12.1 25.1.1-25.6.3 ALL of them it doesn't go away. (literaly like 10 drivers...) When i tried FSR and TAA it made this effect unnoticable, but using FSR and TAA is impossible because any kind of movement makes planes COMPLETELY INVISIBLE.... Somebody please help me fix this.... Or have the shadows in game always been this crappy????? If not fixable, how can i minimize it? It happens the most when the Sun is directly above me. Below is a clip, hopefully its clear enough for everyone to see. I also posted my Options.lua and DCS.log unknown_2025.07.28-05.03_clip_1.mp4 options.lua dcs.log

For AMD users 25.6.1 Anti aliasing is broken. I reverted to 25.4.1 it fixed AA, but now with MSAA on 4x, shadows look trashier, i tried forcing thier quality to ultra in options.lua, it made it somewhat better but not enough. with FSR and TAA on shadows look immensely better, but I get ghosting in WVR and external views when teh camera is moving too fast, and this is unacceptable. Currently I am experincing what the OP mentions, terrible looking shadows on dials and edges in the cockpit, especially when the sun is directly above me. I am going to try a few different drivers now and see what happens

Give us customizable instrument panels and console panel lights... i now want white to match it all!!!! xD

From a game balance perspective, this plane needs R-77s. You are releasing the 1st 4th gen RED plane, with no ability to BVR at the same level as any BLUE plane which is bogus. AND DO NOT give me the plane cant equip them. Russian Mig29As cant equip them. Export variants can. It irks my nerves almost as much as the fact, the only mid range SAM for BLUE is the HAWK.... Can we please try to add things to the game in a way that balances the sides??? I NEVER see this. If one side gets an apple so should the other. Usually in History, thats usually how it works. We got the AIM-120 in 1991 and they made the R-77 in 1994. And here we are getting a mig 29, that people have been waiting longer for, than it took for russia to produce and use r-77s after we released the aim-120 irl

heres a funny trick for the vanilla SA5 u can set up 8 SRs and fix the issue as well lol

mine wasnt doing that, i have sams randomly do this crap all the time, not just this one. Did u try my fix for it? the code was older, and changed since he made the mod. i also cant open ur mission what map is it on

Thats very close to Wadi Al Khirr that right triangle. The pins you have are like right up on Nukayb and Mudasis

That survey is only known locations remember that. Iraq had hundereds of SAMs, EWRS, and thousands of AAA. I find it VERY hard to believe they only had 16 SA-8s and 20 roland. Sam site maps show more/less locations than revealed on the survey. 15 ACTIVE SA-2? I call total BS, its not enough for what they actually had. That survey also contradicts a lot of other sources about the condition of the Kari IADS post Gulf war. Ive been spending a lot of time on google, reading and such. Alot of what was, will never be known, and only what people have actually found is what is. Somebody posted in the tac dcs discord images from a mission against H3, and theres probably 7 or more SA6 sites around H3, was 5 around just the middle lol, and SA8 and Rolands contradict. You will NEVER get it exact, and my mentality with it is very.... OCDish, so in order to even come close to thinking about making a mission id like to make, I have kind of took knowledge from all sources, and placed things in a way that more than likely made the iads BETTER, vs being worse, like most sources claim. While trying to maintain integrity of the key defense areas. Generally, SA-2s, Sa-3s protect cities and infrastructure. While SA-6s and Rolands seem to protect key military facilities like airbases. Designing the area around bagdhad was a total bitch. too many buildings. I had to make zones, to delete scenery that were big enough to fit the sites to spawn in, or if i had options, they were on clear ground. IMO having static sites makes the mission boring, I try to have them atleast move around in the zone they spawn in per restart. Like other guy said, im dying for southern part of the map too. Alot of the fun happens there. Im working on a scenario in the timeline of 1997. Its gonna be baller. This was a cool thread too, helps add to my knwledge base on Saddams infrastructure, something that was too tediious for me right now to dig into lol Also here... https://climateviewer.org/history-and-science/government/maps/surface-to-air-missile-sites-worldwide/

Yes, i already told Whiskey in a Discord DM to fix this. Open the S-200 Launcher.lua, find this line... GT.attribute = {wsType_Ground,wsType_SAM,wsType_Miss, SA3_LN, and make it this... GT.attribute = {wsType_Ground,wsType_SAM,wsType_Miss, I got it to launch the second anything enters the red ring using a P-14, 2 luanchers, and a STR

wWeaponSystem (Main): Not connector nor position specified for WS!! Unit:CH_M2A3, WS:2

He is back!!! stoked to see this reveal.... Ive had my fingers crossed for a few things that could end up being on your radar at some point

Not just one base, do all of pakistan. The game is severely lacking areas of potential Chinese involvement, and this is one of them, Pakistans entire air defence consists of chinese sams and planes, additionally, if power were to sway in the wrong direction in Afghanistan, China might, like the US, have to occupy it themselves at some point int he future as it is on its own borders.....

YES this is happening and its very annoying. everything flickers. Carrier crew, and payloads. Tried turing options on and off. no sharpening no fog, no dust storm, and i cant figure out why unknown_2025.01.18-19.14_clip_1.mp4

Is there a way to report bugs? I may have found one. I had the NASAMS on an airbase of its own coalition, i set the equipment of the airbase to 0 and it still reloads itself. I changed the airbase to neutral, its STILL reloading itself.... probably because it was captured, BUT im not seeing any of the weapons in the equipment list in warehouse....unsure if this is dooable/fixable, not experienced in making mods like that.... I was trying to setup an ammotruck with moose, and can see its ammo going up, with nothing around it. and its on the airbase. i have a second one NOT on the airbase and its not reloading itself. Very odd lol. I didnt want it reloading on the airbase, so the ammo trucks did it lol. Unless i did something dumb, and maybe somebody here could tell me how to force the airbase to stop reloading this thing xD

This started happening to me spawning stuff dynamically on the iraq map. theres about 400-500 units spawned only, and ive even chunked all of the spawns out, and have had to keep chunking them out until the error goes away. i only get the error 1 time, i am going to leave the mission running and see what happens

this is still happening null

What about H1 airbase? how you gonna do h2 and h3 dirty like that? also what about ruwaishid? Also in Iran, Busheshr... that airbase, and area is home to dozens of sam sites....mainly cuz, nuclaer power plant....

WTB HQ 16. There's no good medium range Sam's in the China pack, nor HDS. All we have is an HQ2 which by today's standards is outdated garbage. An HQ 16 would fit the MO. It's a Chinese SA-11/17. It would accent well with the HQ 22 and 17. I also think the missiles are in game, one of the boats shoots them.

aight, so in revements.lua, within the pack objects folder contains a line f.attribute = {wsType_Static, wsType_Standing} It should be changed to f.attribute = {wsType_Ground,wsType_Tank,wsType_NoWeapon,wsType_GenericFort, "Fortifications", }; This way all the revements actually can be spawned as fortifications within sam groups. Without this, u can only drop revements as statics, and spawning sam sites dynamically with them is impossible, if u want randomized group headings. This way u can add them to your sams as fortifications, and use moose to change the group heading and place it randomly in a zone without the sam components falling out of the revements..... the problem is, i changed this, they appear in the ME, but refuse to spawn like this, any ideas why? id like to change this get this error 2024-04-17 23:33:59.581 ERROR woCar (Main): can't load model '' for 'ERO_Revetment_Tank_U' 2024-04-17 23:33:59.581 ERROR woCar (Main): can't load destroyed model '' for 'ERO_Revetment_Tank_U' when i get home from work ima try copy pastaing the Bunkers.lua syntax, and use it for the revs and see what happens. UPDATE: it seems to have worked lol. i took Bunkers.lua, and copy pastaed it into a new file and replaced all the needed values with what they needed to contain all the revements as fortifications. Just a forwarning dont use them with EWRS in MANTIS... aight so this got finnickier than i thought, when trying to return the Threat level of the groups, or even using GROUP:isSAM(), after all the sam components die, there isnt any type of return, true false or nil. the threat level will just vanish, so i feel like components of this mod are hardcoded into statics

has this been updated for 2.9? or work with 2.9??? i had to uninstall alot of mods to get my game working after that. had crashing on my server

would really appreciate some kind of way to mass download and install every one of your mods, having to keep up with updates, in a busy Real Life setting is a pain in the ass. it sucks having to download 1 at a time, and with my inability to keep up, i lose my spot!!! if not a 1 button quicky... at LEAST make is so you can mass download an entire countries worth of mods... with one click.....

All i want is some similar runaways that are the same on each map. Like if they made a new map that contained saudi arabia and iraq along with the top corner of this map, I would be able to drop a carrier in the water in essentially the same spot, then have the mission end and reload the next one once everyone is landed on the carrier. This upset me about the new sinai map they coulda added ramat david but didnt. can literally roleplay land and switch maps via scripting and stuff lol... As long as a new map is made that kind of over laps others they could probably do cool things with that in the future too lol.

I cannot seem to get the SA-5 to fire while at max range. It will fire at Targets within 75nm. Others have had this problem too. I tried a few things. Fresh Saved Games folder Full Repair With Skynet Without Skynet In DCS with the Sam site set to Alarm Red and Weapons Free Engage Air Weapons.... with the tin shield, with the p-19 with both, without both... I dont understand why this is happening it used to not do that. Yo can look at old grim reaper videos of them testing the SA-5 and it actually shoots at them much earlier than i can seem to get it now, and i cannot figure out why I jumped in the m2000c and flew at it, with no scripiting or anything just normal DCS.... It didnt start tracking me until i got to like 100 or less NM and then fired at me at 85 nm its threat ring is around 130-40 nautical miles. I can see why it would be off sometimes but its around the 70-85nm range it starts firing no matter what altitude its at....