Guppy

Hey all - I spent sometime this morning trying to find this answer but could not, but I thought I had seen acknowledgement/a thread on this before: Deferred Shading obviously is not working correctly in relation to runway lights/LG lights/cockpit lights, ...lights in general! Is there any acknowledgement from ED on this that it is a bug/problem. I tried flying with DS off... and well the game looks meh compared to it being on. Just curious if there is likely a long wait or not to see this get resolved. Thanks!

Not to derail this conversation... but F-15>Flanker. But it doesn't matter, once the Hornet comes out we'll be toasting you with that. :joystick: haha

Hey all - love the mission... I'm constantly playing it. Some feedback... the Russian AWACS on the blue side gets ridiculously annoying late in the game. I assume this is the EWRs that are setup? To me, this becomes game-breaking... instead of relying on assistance from them I just shut off in-helmet sound, which should not be the case; especially when there is no GCI. Just my 2 cents!

My recommendation would be to allow 120Cs from Blue starting base. allow the pro/con of taking longer to get to combat but having the superior weapon. or allowing a rearm via c17, etc.

Updated, in red. :thumbup:

When I search the forums there appears to be a plethora of random tidbits of information on how to export MFDs, setting X/Y coords, etc. However, is there a beginning-to-end tutorial on this stuff? All of the information I have looked up appears to be as if you already have a base knowledge of how this stuff works. I do not, and I'm having trouble figuring out where to start. Google searches are similar, too. Any assistance to find a export/.lua for dummies would be helpful.

Hey all - I believe I have a repeatable workaround: Step 1: Launch game - Start a single player instance. Typically I use Instant Action. Once flying exit back to the main menu; do not quit the game. Step 2: Find the server you wish to join and join it. (This will likely take less than 5 minutes) Step 3: Do not select your aircraft after you finished loading - likely the aircraft selection grid will be reacting slow, instead click disconnect. DO NOT GO BACK TO MAIN MENU Step 4: Join the same MP server again. Once it has finished loading (should be less than before) click the aircraft you wish to fly and click fly. In total this takes maybe ~10 minutes and is much better than the 20-30+ minutes it used to take. Hopefully this helps!

Disable SLI... That's what I had to do and I get about 80+ FPS. Check out my signature for my specs.

All - I continue to face long loading times connecting to a variety of servers. Specifically 104th is atrocious and usually takes 2+ times connecting/reconnecting. But much of the servers are taking a while to connect to. Or after I have connected the aircraft selection screen takes forever to load and jumps around. Any ideas how to mitigate this? It's certainly not my PC specs (located below) or my internet connection (120Mbs cable). Thanks!

I posted this in the wrong place - please delete.

Everyone cancel their downloads! It's my turn... it's taking forever! :)

Does any of this matter once the F-18 comes out? Are any of us going to be flying the F-15 anymore? haha

Sorry, you misinterpreted what I meant - that's my fault. I meant it will end, as in, the initial 2.5OB will come to a close and be promoted to "Production Release"(IE: 2.5.XXX, i presume). and the 2.5.xxx OB channel will continue as a place to test future updates before promoting to the production-release channel.

As I understand it, on 1/31 OB will be released following the detail from the original post. An undisclosed amount of time after that OB will end and we will be left with a stable version and a beta version, for future changes. Fully agree!

I suppose that the 99.99999% of game developers when asked for a "Release Date" aren't actually giving you what they believe to be their "ready product". Instead you're just getting a version of the product. :doh::megalol: Okay, guy. EDIT: And to expand a bit. I'm totally fine with ED "releasing" their product this way. However, I believe a little more transparency would have done well back in December when they initially offered up the end-of-January time frame, to keep everyone's expectations aligned. Managing expectations is important especially when something, as exciting as this, is to be released.

Yeah, I fully disagree with you. ED stated: "Releasing", in this context, sounds an a lot like a production-ready product. I think this is a slight fault on ED's part. They should have stated, "Releasing to Open Beta - additional details to follow" or something to give just a tad bit more detail to make sure everyone's expectations are aligned. I work in Project Management/Delivery and ensuring everyone's expectations are aligned is the single most important aspect. With that said, it might not matter. My only fear is that the community is already separated between multiple versions of the same game... I hope that won't be the case with a buggy Open Beta. Of course, it might not be buggy, but "beta" always means bugs, to me.

FYI I do not believe 2.5 utilizes SLI (could be wrong), I certainly know 2.2 does not.

If we are going to wait then I require one video, from them, every day until its released! :pilotfly:

I'm a little disappointed 2.5-Open Beta is being released on the 31st and not the full (non-beta) release. For me, it would be better to release the Open Beta earlier, get feedback, resolve bugs and still have the final hit "release version" on 1/31. To me, this is not meeting the 1/31 date; but my expectations could be out of wack. Oh well, it is what it is... it'll be here sooner than later!

It's too late... I messed around with UltraMFCD and didnt exclude it from virus scan and it killed everything DCS... I'm now reinstalling 1.5 :(

Before I reinstall DCS I want to see if anyone has encountered this issue. My anti-virus (Bit Defender) flagged UltraMFCD as a "Act4.Detection" malware. When I researched this issue it seems as though its not entirely uncommon. However, because it effectively "injects" itself into other files it has effectively tainted major components of DCS. To the point where I cannot even repair or launch the game. Has anyone encountered this? Has anyone solved it? I've restored all of the files from quarantine but it still wont launch.:mad: EDIT: I had to completely uninstall DCS and I'm working on reinstalling it now. For anyone planning to use this make sure you exclude this app and DCS directory from ever being scanned.

So it sounds like if I have both 1.5-release and 2.2 installed I might as well uninstall one of them as I only need one to move to 2.5. I only really fly in 1.5 as I use 2.2 to stay up to date with graphical improvements. So bye bye 2.2!

Excellent - and what are our alternatives if it does not work anymore because the developer is AWOL?

https://ultramfcd.com All of the marketing materials show each of the "MFDs" on a single, main display. How does this work if I were to power two 8" monitors for my Thrustmaster MFDs? I'm trying to understand how this works without having to mess with the .lua files. Any help/explanation is appreciated. *edit* Just saw this: Multi-monitor support UltraMFCD's displays can be dragged freely to any display connected to your computer - even those on which DCS is not running. The rule is simple: If Windows is aware of the monitor, you can freely drag one or more UltraMFCD displays there Is it really that easy? I'm waiting to configure all of this until 2.5 comes out.

Listen... I havent eaten since Friday. I'm on a hunger strike until it releases. I recommend we all hunger strike.