polygonpusher

Thank you ED for the unexpected and timely support for the Nevada terrain fix! Will there be a similar hot-fix for refueling - in that once you disconnect it is impossible to rejoin and give it another try without restarting the entire mission. With deadlines, I understand if you cannot. However, I'd be grateful to know if one is in the works. ~ If I don't get better at taking on fuel, my Wife's going to give me the callsign "nervous filly." last time I let her watch me practice ")

+1 A big salute, and Thanks to you Shadow. We're grateful to have wolves protecting the flock...

A-firm.

My lovely Wife is even looking forward to going through the training missions on final release.... *What can I say -everybody loves the avenger cannon :)

I know that I've been posting quite a few questions here, and some concerns about performance issues... Be that as it may, more importantly I want everyone at ED to know just how much fun I have been having with this sim. It truly is shaping up to be a masterwork of simulation. As long as I've been into pc gaming -this gentlemen, is what I've been waiting for... :) *could a forum editor pretty please correct my misspelled thread title... :( No problem. :) -EtherealN

Wilco Nate, back to the manual again :)

Correct. There is only one SPI at any one time. If you set the SPI using instrument "A," (TSM up long) then you set the SPI again in instrument "B" (such as the Maverick) (TSM up long)... You have replaced the SPI you set with sensor "A's" with the SPI set using sensor "B." That's why I say, if you have the target centered in the SPI created with the targeting pod, why would you want to replace those coordinates by defining the SPI again with the maverick (TSM up long?) Once the Maverick is used to define the SPI, if it wanders off course you have lost your target point. Keeping the Maverick slaved to the targeting pod defined SPI, means that if the Mav wanders off target, you can always slave it back to the SPI again. The SPI stays fixed no matter where the Maverick seeker head goes. If however you re-define the SPI by using the Mav, the SPI now follows the Mav seeker head, the SPI and the Mav are no longer independent positions. That's my understanding of things in any case.

Yes, and that's what I see some people recommending. . . slaving all to the Mav SPI, then locking up with the Mav. That's why I disagree... You don't need to slave all to the Mav's SPI in order to use it successfully.

Yes, but if you set the SPI through the Mav, you loose your lightening target position...

No, What I mean is, if you designate the SPI with the Mav, and the Maverick wanders around, the SPI then wanders around with it. The SPI is slaved to where the Mav is pointing in that case. If however you designate the SPI with the targeting pod, and only slave the Maveric to the target pod's SPI, If the Maverick looses it's ground stabilized position, it won't drag the SPI all over creation with it. The SPI stays put because the targeting pod "ownes" it. I'm butchering the concept, but does it make sense?

After locking up a AAA with the targeting pod, I thought I was Hotel Sierra as I got ready for a GBU to come of the rail... Until the CMFD showed a nice close up of a turret swiveling lazily in my direction... Any other cool moments?

I found myself trying to use the track-ir visor to block out the sun, which in a way i suppose it did!

Windows XP users reported a crisp picture, however on Windows 7 it's blurry.

The way I see it, there should be NO reason to HAVE to re-designate the SPI with the Maverick. I set the SPI with the targeting pod, and I want it to stay there. That's the whole point of an SPI, you can set it with one sensor, then "use" it with another. If you set the SPI with the Mav, and it wanders off - there goes your nice stabilized point... Slave Mav to SPI - Yes... Re-designate SPI with Mav - No... Am I way off base?

two.

Yay! Thanks Wags!

Thank you everyone. Narrow FOV does work a little better and the idea that it's using a digital vs optical zoom make sense, but even so I can't imagine that something designed for danger close situations would be so "fuzzy." The CMFD's are set at 512 res, and my overall res is 1920x1200. Any testers have any ideas? Is this a "to be implemented" feature? I wager it's just a beta issue. Thanks for the input everyone.

When it is blurry it usually is at a high zoom level, but not always. Does anyone know how the CCD sensor usually works? What is the "normal" behavior, and is there anything the pilot can do to refocus it?

In the screen shot I'm using the CCD daylight camera, which -in theory should be just like any other "digital camera." Unless I'm very wrong, there must be a way to "focus" it... Is it a "to be implemented" feature?

Please see attached... Will it be possible in the final build to use this, or some other method to bring the TGP image back into focus (as one would focus a camera - make it less blurry?)

+1

Good stuff, Thanks!

Understood! Thanks so much Frederf! Btw, do you know what the release mode PLT OPT does exactly? It's mentioned in the manual, but not really explained. Thanks...

Thanks Viper, Maybe next time.. :)

VCR style replay controls, replay markers? Something else I wanted to fire off on my lunch break... Would it be possible, in this build or in future DCS products to include replay sliders for navigating to specific points in the replay? Along those same lines, it would be cool to have a replay marker button that you could press in game when something neat happened - so that you could then later navigate to the mark point(s) in the replay... I'm guessing there is some technical reason why a replay must be watched or fast forwarded from end to end - something about it being generated on the fly... In any case, your thoughts? I'd love to have some standard replay controls... Thanks, D