Frost

Will there be some kind of announcement prior to the early access release of the Mig 29? I'm absolutely and definitely going to by this module, but I'd like to buy it for the pre-purchase price and as late as possible. PS: My budget has gotten a little tight after I've granted myself a Moza AB9 FFB Base last month -which I can only recommend by the way. Finally I can switch from F-16 to UH-1 in an instant. Which is actually much more worth than the force feedback itself. For chopper guys this is the only way to go anyways.

First of all, I meant F-15E, not F-15EX(embarassing). A year is ok, but I have so little time for DCS and so many modules to fly. Therefore a year can be very short in effect. I'm kinda leaning torwards a refund and buying Afghanistan.

I just want to know one thing. Will the F-15E work in the future? If so I'll keep it even though it will stay EA forever. If the module's functioning can't be guaranteed I'm forced to apply for a refund.

But what does the date have to do with the Radar? The ground Radar works with true headings and coordinates I suppose. Both never change. What is the reason behind the inquirie?

Question: -do all modules check the system date? -does it communicate directly with the system, or does it get this kind of information relayed via DCS -and if so, is there a hotfix possible to "fool" the module with a faux system date? PS: Making the functionality of the modules' radar dependent from a date doesn't make any sense in the first place. I could understand anything that works with magnetic headings, or FMC databases, but a radar?

This module is basically like a loved one in a coma and on life support. Even if it starts breathing again by itself, it will still be in a coma. But you just can't let that thing go. This whole situation is a frustrating mix of stupid ol' hope, wanting to let go and an annoying "leave no module behind" mentality.

I only need to know one thing; does it make sense to "trade" the F-15E for the Afghanistan map or should I wait and buy Afghanistan at a later date? With other words; as much as I love the F-15E and as much as I want to keep this great module, I just want to move on and therefore I want to know how dead this thing really is and how probable an actual resurrection is. If it is dead for good I just want to know it, so I can finally start coping with the loss of this great aircraft. And the Afghanistan map wouldn't be the worst way of doing so.

The thing is, that it doesn't even matter who is wrong or right, or in which amount both are at fault, in this particular case. The elephant in the room is the fact, that ED obviously didn't made their contracts -or whatever is legally necessary to guarantee the functionality and the progress of a particular product, tight enough so that stuff like this couldn't even happen in the first place. That's the purpose of a contract isn't it? So that in a worst case scenario -like now, there are no questions about what to do or what should happen. A contract is basically an emergency checklist, that tells you what to do in a scenario where you haven't the luxury of time to figure it out by yourself and at the cost of your passengers/customers.

And even more potential content creators are a bad thing then? I don't get it. Aside from that, it could've been a nice suprise and a gesture of acknowledgement to the people that trusted them and their product in advance. But on the other hand I really don't want to make too much of a deal out of this whole thing. I have, anyways, too many aircraft to learn.

My very first thought in this regard.

First of all, the "flag" is always showing three whites by nature. Which is usually supposed to indicate some sort of failure, which in turn was discovered by the HSD BIT. Secondly, what it shows or doesn't show, doesn't seem to be in any way connected to the actual HSD BIT, or rather the pushing of the HSD BIT button, since I also wasn't able to run an actual BIT in the first place. And thirdly, and that one is probably the strangest one, turning the caging knob of the SAI(Standby Attitude Indicator) also rotates the HSD BIT Failure Indicator. It seems that everything around the HSD BIT and its associated buttons and knobs is wrongly "wired".

It's not so much about the release itself, even though I'm greatly looking forward to it. I just wanted to know how much time I would have left to buy this gem at its current discount. Should probably just buy it. But thanks for the replys

I suppose so. But is there any word out when that could/would approximately be? I mean roughly. The next few days, in around two weeks, this month? PS: EA stands for what? Or just a typo?

Until when will the F-15E be pre-orderable?

Ofc that is the way how NVG's work. That's why I also asked if there's a way to tone the tankers position lights down. I'm sure that in reality you either don't have to turn the NVG's sensitivity up as much as I do to spot the drogue, or the tankers lights are much more toned down/NVG friendly. With NVG's on even only formation stripes would be sufficent enough to get an idea of the tankers attitude. Also irl there would be actual communication between the tanker and the refueling jets. And as soon as the entire refueling party would have arrived and wait in line there iwould be no real need for those bright/obstructive position lights, since you can see everything as clear as in green daylight. Either way, I tweaked the NVG file a little. It doesn't really change the contrast or anything what I was asking for, but now the NVG shader covers 95% of my screen which makes it at least in some way a little easier for me to refuel, since my "NVG enhanced vision" now also spans into my peripheral vision and I can see a good portion of the receptible tip in the corner of my eyes. Very helpful for situational awareness, at least for me. And it even makes it easier for me to spot the drogue in the first place, even with the same NVG sensitivity. Since the entire screen has more or less the same brightness. I've changed those values in the PostEffects file called NVD_common, to those that are shown here #define MASK_SIZE (0.7/1.2) Directory: \DCS World\Bazar\shaders\PostEffects\NVD_common Aside from this I wouldn't touch anything in the game, neither via the UI nor through mods -in terms of making DCS anything but realistic. I have everything on realistic including wake turbulence etc., but the NVG's might be a little bit too tiny in my opinion.