BlueAngel

Oh boy, I thought I was alone in this. I am not a "super dogfighter", but I could easily ID targets at about 5, 6 or 7 miles out, no problem. Since this update, I LITERALLY cannot see anything as close as 3 nm. That's just not normal or even realistic. Something must have changed in this last update, maybe in the last one, I can't say because I only returned to DCS to fly the F-14A yesterday after a brief break from my computer. I also like to see people popping out charts to attempt to explain how a videogame is trying to be realistic. Even considering realism is a valid point, 3nm and no visual on locked target, something must be wrong... even according to those pretty charts.

Can someone explain to me how to do this? It's just not working anymore.

Solved the issue by deleting the Saved Games/DCS folder. Thanks for the support, btw. I was about to open a ticket but the system encouraged me to open a thread on the forum. Next time, I'll skip the suggestion.

Hi all. After the last update, whenever I join either a single player or multiplayer mission, I ALWAYS get a freeze of about 3 minutes. Searching the system processes, DCS is "not responding", GPU activity is null. After this time waiting, the sim eventuall resumes and I can fly normally. But, if I restart the mission or rejoin the server, the same 3 minute frozen time. Can anyone help? Is this a known issue?

The question is, you guys keep trying new things with each version. No issue there, it's a Beta and you need to try things to sort this thing out. But, you must understand that changing the command lines and not explaining what is new WILL break skins, including those posted on ED's user files page. Therefore, why not just create a post like yours explaining how to solve/remove them before people start banging their heads on walls figuring it out? That's just my point. No offense meant.

These constant "bort number" change is a disrespect for those that spend hours creating textures for DCS. I sincerely hope ED stops "inventing" the numbers designation over and over and having us guess how to remove them. I understand ED doesn't support mods, but they can at least explain how to change these particular lines in the lua file.

No one saw this?

There's something wrong with the PSDs of the F-16 paintkit. Not only the dirt effect is too heady (I know I can increase transparency to minimize it) but at least one template, I believe Fuse 2 always gets too dark when exporting the DDS texture. I've tried different DXT options, no matter what I do, it's always darker than all other textures. I've downloaded the paintkit yesterday, so I supposed this was fixed from the early version. Perhaps someone knows a workaround?

The moment you used Star Citizen as an example, you completely lost your point. Eagle Dynamics is nowhere near what Chris is (not) doing. That's a very poor example.

I see. What does it do, you know?

Is this an error?

First of all, thank you for not preferring Hoggit over ED's official forum for an official update. It kind of missed the point last time, no matter how important that message of yours was. As for the update itself, these are all good news, basically saying ED is aiming towards quality not quantity. Like I said, I prefer to wait for good updates, than receive bugged, memory leaking dumpster fires.

Once again, Hoggit shouldn't be the source of public support/announcements...

I think people are more bitter from the lack of comms than the lack of a module, to be honest. The unnecessary "secrecy", the lack of communication, the "maybes"... I sincerely think ED needs better PR here (not hoggit), that can take the pulse of this community. A thread about a module is derailing to become a storm of "demands", anger and bitterness.

So, after all this drama, I'm still confused. Wasn't there a notice we would get some news today?

It's in their best interest to do so. Because they happen to earn money by selling modules. Just take a good look at every single previous released ED module and you'll see.

From my experience with DCS World, it has always been like that. Make or break. Maybe not shattered to pieces like you say, but cracked in multiple occasions. But this is an old discussion for another place. Since you halted all production for the Viper and Hornet, at least make the Supercarrier worth our while. Again, delay it if you have to. I prefer a longer wait to another broken module rushed to launch.

True, but they didn't show anything about the approach or other procedures. There are... what? A take-off procedure tutorial, a pomo video and a FAQ page? Not much hype for such a long waited module, am I right? Either it's delayed or most of the announced features are either missing or bugged. I prefer the delay, to be honest.

You despair? There's no desperation here. Just a joke that turns old pretty fast. Sorry if I want to play the game following its procedures.

About the April Fools joke At first, it's funny. You operate the gear lever, some slot machine animation shows up on the left MFD, then you get a random failure. A nice joke... once... Did anyone at ED actually thought this is game breaking? I actually stopped flying the Hornet and the Viper until this joke is over. I consider myself a joker, like pranks and all that. But operating the gear and get ejected gets old pretty fast. Thanks for the laugh in the first few minutes. Can you please now deactivate this? Honestly, this is just annoying now.

Well, if you use the standard grey tone on the regular USAF scheme on your paintjobs you can add it fine as it is. BUT If you use any other color scheme, it wont work, since this digit is hardcoded into the wrapping texture. In my opinion a lazy way to do it. You can't change anything about it, including colors or the background mask. Might as well consider this a "wip" case and nevermind painting this plane until their modeller/texturer finishes his job.

Hi With the latest update, now a single digit is added with grey background and blue tinted number, even with this fix. Can we remove this new "zero"?

Sorry, but I don't think that's how that's syntax works. I think that's an instruction to search the current folder and if the texture isn't there it will place a "missing texture" placeholder.

Is there a way to remove all bort numbers on tail, nose and top? Really annoying on some liveries as it's also poorly implemented with no alpha channel, just a lazy number set with painted background.

You don't need to confirm Altitude, only LAT/LONG. The third step is excessive. It needs to be done in the first two minutes of normal alignment. It is not required with the Stored INS option.