VAF [136] Striker

I did post a track. If you bothered to look at my first post it's there. And I let him know in a PM that it was there. Unbelievable attitude on this forum still. Makes me wonder why I even bother.

Any word on this NineLine? I just checked again after this patch and the problem is still present.

It's super easy to verify, it's pretty much every building on the map, pick a spot. All they need to do is put "explosion in zone" in various places on the map and they'll see it. I added a track file though. I just picked a random area and started bombing with GBU-31 3/B's.

As I say, close, not completely. You can damage scenery object buildings but it takes a lot of bombs now. I tested all of the maps that I have, SA, NV, Marianas, Normandy, Syria, PG and Caucasus. The damage model in most of the maps seems fairly consistent. Drop one GBU-31 on an oil storage tank and it's flattened. In Caucasus though, I dropped half a dozen of them on one small storage tank and it was only damaged by a percentage and not destroyed. This problem did not start until 2.8. We were able to destroy all or most scenery object buildings prior to 2.8. Building Test Track Setup-20221108-150453.trk

Pretty much what I figured. Thanks gents!

I searched this topic and did a general Google search and haven't found an answer regarding this problem. Have always had issues with mods in the past as some don't pass integrity and others require everyone to have them in order to just be able to see them. So I'll post my question here. We have 3 dedicated servers, two for group missions and one for training. I would probably test this on our SUPT server first before handing it off for submission. We have to carefully analyze any changes we want to suggest and they have to be tested thoroughly before being submitted. 1. This mod obviously requires that you have it installed on the dedicated server, and in the mission file you're running, any other files or changes required? 2. Does this mod require that every client that connects to the server have it installed as well? 3. What will happen if they don't have the mod installed in their client files?

Right now our Naval F/A-18C group is pretty full and we're bringing new guys up to speed on tactics and systems. Doesn't mean we are closed to accepting new Hornet people, however we would definitely welcome more dedicated F-16C drivers if interested. The 111th have become real masters at A2A and sneak attacks and they study and know the aircraft systems inside and out. If you want to learn from some super dedicated Viper pilots, here's your chance!

Fixed for me too!

You guys aren't alone. It's happening to a lot of people in our group too. I've been told it's worse in VR. I'm using TrackIR and it seems like the time of day or shadow angle has a lot to do with it. I was taxiing at Kobuleti and it was happening so bad, 75% of my screen went black. BigNewy posted in another thread that they have reported internally that this problem is present. Hopefully there will be a fix for it soon.

OK, thanks. I may message one of the guys tomorrow and get some confirmation on coming updates.

I thought that the ATFLIR was already part of updates already done. That's not the case?

Absolutely, it seems like it has something to do with the auto focus under certain lighting conditions.

OK, so we've been struggling with this problem for awhile now, and this can't be the way that this pod is supposed to perform. I understand the zoom part completely. It doesn't have anywhere near the range of the Litening pod. But the clarity is just terrible in certain conditions. In direct daylight without clouds, the images in the pod look great. Add some low heavy clouds in morning or evening and it just becomes useless. In some conditions the ground vehicles are so fuzzy, they just look like blobs of white, almost like bushes at a distance over 10 miles. What is going on with this and is this going to get addressed? Or is it something we're not getting about the pod? You can see that close it it's crystal clear, but if you're out at 15-20 miles it's just useless.

Thanks for everything Wags, happy Birthday!

I've updated the link on the other thread in the main recruiting section so it's persistent to our Discord server now. It's temporary permissions when you join our Discord channel so it can't be abused by trolls, but the permissions can be changed when anyone with admin privileges is on.

Yeah, we're going to use this solution as well MTrenda. We've kicked it around for awhile and it's really the only option at this time.

RGR Pikey, I was hoping that someone had played around with the LUA and knew how to modify it. I'm guessing that it's buried deep in the code and not accessible through just the general LUA files.

RGR, we know it can be done that way but I was looking for another solution.

Is there a way to actually change the turning rate of the carrier or any ships for that matter? We have the carrier doing a box pattern in our missions and it's apparent that the carrier has one turn speed only, as quick as it can. So if the carrier is in a 90 degree turn the deck is pitched about 30 degrees. I'm just wondering if there's any way to alter that turn rate in degrees per second or however it's set.

Our New Promotional Video

Love the P-38 and fully support anyone that would decide to develop it!

Thanks for reporting this.

Beirut after being hit with multiple JSOW-C's in the same spot and Mig-21's just taxi right over the spot. This seems to be an ongoing problem, sometimes OK for awhile and then back again with no answer in sight. We bomb a runway or taxiway and right now the AI just taxi over the crater on the taxiway or take off from the runway as if there's no problem. If you're a client and you try this you'll fall in easily. It's happening on the Syria and Caucasus maps. Also, the repairs happen way to fast now. It used to take about 10 hours for a runway in Caucasus to repair, now it's an hour. Same thing in the Syria map and in PG map. I don't understand why there's so much inconsistency in the maps as far as repair and damage modeling is concerned. Also, the AI still do not respect the ownership of an airfield. Late activation enemy will spawn even though the airfield is owned by another coalition. So we essentially have to turn off all the reaction aircraft to make the scenario work. Really frustrating stuff.

I goofed up on my table and had the timeline extended for both the 15 and 19. It should be closer to the actual but if it's not please let me know. This table is really mainly for mission designers. If you want to pick a specific year, then you can reference the table and restrict the equipment to what's on the list. By the way, I updated the spreadsheet file to have separate sheets and did a better job with the colors.

This is a very general guideline based on public available information cross referenced with DCS World Encyclopedia information. I'm 100% certain that there are mistakes, so please don't take this as absolute, but it will at least give you a general idea of when systems were available or fielded in real life. I've included most of the military aircraft, including helicopters along with ships and SAM systems. The asterisk on the airplanes denotes client flyable. If you have any information that can be used to correct what I already have, please feel free to share it with me here. Sorry about all the different colors. I'm going to update it from time to time and make some improvements in the layout when I have time. I'll add important units if someone points it out, but I'm not going to add insignificant items like soldiers, light AAA systems or most of the ground vehicles. If it's something like a main battle tank that's important to have, I'll consider adding it. If you would like something added, please tell me and explain why. DCS Unit Era Table V2.ods DCS Unit Era Table V2.pdf