Dun_Aenghus

I've been flying since SSI's Flanker in 1995 and ED are attempting to address the issue by introducing Vulkan and making other improvements. Unfortunately bad things like the Hawk can happen, though I find the state of the MIG-21 quite ok. It's a niche genre and a lot of US flightsim companies folded in the late-90s. Personally I'm happy it was just a module that was lost, could have been a lot worse. What we have is truly exceptional and they'll make it better.

Very much agreed, hope to see it added as well.

Saw several of them flying around the airport in Krakow. Would be great to have them added to the Polish.

This is on the cards - screenshots showing a full crew on the deck of the Stennis have been posted.

It has been bugged for months, really wish they'd fix it, surely it isn't too hard to get it sorted.

Also really hoping this gets fixed soon.

It would be nice if the F-14, F-4, C130, SU-24, etc, was only added to Iran with correct skins provided. Right now IRIAF F-14s are in US Navy colors. I believe a user has already made an exceptional selection of skins for the entire IRIAF fleet. It would be great to see that added. Likewise with skins for UAE F-16s, Saudi Arabia and so on. In the Caucasus, it is possible to represent all of the regional players - proper Turkish, Russian, Ukrainian, Georgian skins. In the Persian Gulf, much of the Iranian opposition is either absent from the faction or flying in U.S. skins.

Agreed, this fix really can't come soon enough. We've needed this for years.

It would also be nice to have a French Airforce tanker to pair with the Mirage.

Any idea if this has been fixed in the latest update? It would be great to finally have the 135BDA working with the drogue.

My motherboard can only take up to 16GB and I was hoping to wait another year or two before upgrading my system. Hopefully they can either make this official or fix it. As was said before, many users are getting good perfomance in the Caucasus and Nevada. Surely the Persian Gulf needs some optimization. The Caucasus was the same - stuttery and RAM intensive when it first came out but then it got much better after a few updates.

Well, I tried that mission and I had no problems taking off. Are you sure you are using the correct procedures? Opening the engine grids? Then holding the breaks and going full throttle before applying the extra power boost to get off the deck? It was tight but I had no real trouble taking off on that mission. Maybe reduce the fuel a little bit.

Same happens to me, no idea why! It only seems to happen if I select the 120 before locking a bandit.

Ugh, that looks pretty frustrating. Could we get some information from the devs about whether those of us who purchased the Persian Gulf map and are having problems will now have to upgrade to 32GB RAM or if some kind of optimization is incoming?

Rain, did you download and give Process Lasso a try? I still have the same problem and it's helped a lot. Still not perfect but the PG map is playable at least. Frustrated that I still even have to use if with 16GB but it's worth a shot.

Hello Spokey, are you pressing U when you are in line with the catapult? Also, are you lowering your launch bar beforehand?

This is an asset we've needed in DCS for years, hope it gets fixed soon!

Surely there is still something wrong when some people are using 99% of their memory on PG and all of the other maps are running fine, whether it’s 16 or 32gb.

I have the exact same problem - I turned all of my settings down - textures to medium and terrain to low. For me the preload radius didn't make too much of a distance. Actually, after a few minutes, it was using up 15.5GB of my 16GB RAM while barely touching my CPU. I took some advice and downloaded Process Lasso which helped distribute things a bit more. It also offers the ability to "trim" RAM back if it's using too much. There are some further tips on how to use it here. Now, RAM gets to 13.5 or 14GB sometimes but rarely makes things unplayable like it did before. Still, I'd rather like to find out what caused the issue in the first place. Absolutely no problems with memory on the Caucasus and NTTR maps. I really hope some more Persian Gulf optimization will be incoming.

Well I took off and did everything alone and just viewed the wingman to see if he finally took off. He did and then crashed into the sea swiftly afterwards.

Are there any plans to add desert camouflage to the tanks and other units we already have? For example, the M1A2 and T72 are still European green and stick out.

This one is really frustrating. The AI do finally seem to take off after about 20 minutes and then they swiftly crash. Can someone at ED prioritize fixing this one? It's pretty much impossible to take off with wingmen.

Agreed - it would be nice if all of the campaigns that shipped with FC3 could be updated for 2.5. The single missions for the A10C and other modules are also screwed up. I've edited several in the mission editor but it would be nice if the content worked properly for users that paid for it, despite the work involved in transferring everything to the new version.

Does it also happen to you if you look at other units? For example if you switch to view a far off AI aircraft with the F2 external view? For me, sometimes the terrain reloads quickly but on some occasions I'm stuck with ocean beneath me for 30 seconds. That happens more often after viewing F10. Frustrating because this didn't happen with earlier versions of 2.5.

I have the same problem and it's only ground textures affected. Setting terrain textures to low helped somewhat but the problem is still there and it's really bad after viewing the F10 map or other units far away.