Noluck

You new guy's really need to read the thread(s), not just post on last page. Looks like this is a dead issue now... ---

NEVER put any user files in the c:/windows, c:/Program Files or c:/Program Files (x86) period. That is asking for real trouble down the line. I keep my own mods, OvGME, documents, DCS downloads and all non official files in a folder under ../Documents and Settings/<your user name>/Saved Games/My DCS Files/. where I have a My MODS folder along with an OvGME Backup folder. Of course, the actual official DCS saved game is in ../Documents and Settings/<your user name>/Saved Games/DCS/. ---

I have to agree with OP. In external / F2 view the transition between looking from the rear to front is too 'sharp'. I flew MP first time since update and the F2 externals almost blew my ears out. I had to go and decrease the world sounds down at least 5% or it was overwhelming. Never had that problem before. However I really appreciate ED fixing the DDI and MPCD readability. Now we have contrast control, day/night on MPCD and more. Not to mention the awesome updates to the TPOD and the Ground Radar. I care more about these issues than some sound upgrade that changes everything else. ---

Thanks for the help everybody.

Standard default DCS binding to the WH stick second detent/switch, no software. I'll try to just press the weapon release button. Chuck's and other info says to use the trigger. Interesting conflict of info here... I'm still learning so no problem, I just want to make sure I doing it right. Thanks for the info.

The switch labeled in the NATOPS is the "RAID/FLIR FOV select button", the one I have mapped on the WH throttle, left side push button in front, pretty much same as the actual. Prior to the latest OB, it did perform that FOV select function with the SOI on the FLIR display. After the update, it does not. I'm confused, the switch is labled as above "RAID/FLIR FOV" but will not affect the FLIR display if a MAV is selected? Now I have to take my hands off HOTAS to change the FLIR FOV correct? I'd rather have it back the way it was. If it's like that with MAV's in the real Hornet, then so be it. Thanks for the information. ---

Thank you!

Interesting. I designate and then a lase target. Lase quits also when you let go of trigger. However, I can keep the trigger pressed and launch a MAV and let go of the trigger and it will continue to lase until impact. Also, I have seen no affect on a TM Warthog stick whether you set the trigger to activate on the first or second detent. I have it on the second, a lot less chance of a accidental A/A weapon launch and second detent is used in the real AC as far as I can remember. ---

Prior to latest OB, it depended on which DDI the SOI was located. Either the MAV or TPOD/FLIR. The "RAID/FLIR FOV select button" affected that SOI selected display. Now it only affects the MAV, no matter the SOI. I do not think this is correct. Why would the NATOPS call the button on the throttle as mentioned in quotes above? Now I have to take my hands off of HOTAS and and manually press an OSB to change the FLIR FOV? Makes no sense and I believe it is now in error? ---

The external/F2 sounds on the F/A-18... well they are no longer working correctly. As soon as you rotate to forward view off of the 3:00 or 9:00 position, forward looking back, there is now no sound at all?

I was curious of the same thing as I have witnessed that idle 'issue' before. Makes sense now. Thanks ---

In my observations in the designate/lase steps. I'm just learning the TPOD as of last week. I see that there are changes? Just trying to get this all down and learning. 1) FLIR is selected on RT DDI and timed out 2) you have to press TDC designate and then 'pinky un-designate' to get FLIR or other video to show up at all. Strange... 3) ensure laser is enabled using RT console->Sensor Panel->LDT/R switch 4) select [TRIG] on the DDI using OSB, will now be boxed/highlighted 5) with SOI on that DDI, slew the diamond to the target with throttle TDC 6) press TDC/designate button, FLIR diamond now locked onto target and stabilize 7) press and hold trigger, lase will start. Let go of trigger, lase will end. I ask why, I now do have a target designated? I have to press and hold the trigger *and* fire the weapon (AGM-XX for me) and now TPOD will continue lase without holding the trigger until weapon impact Also, after the last update to OB 2.5.6.53756 : you can no longer change the FLIR FOV using the throttle HARM SEQ/RAID/FLIR FOV push button. It now changes the selected weapon FOV no matter if SOI is on the FLIR display or not. It used to work. ---

Just another example of F/A-18 'updates'. Fix one thing, break more things. Why the main and very important displays used, the DDI's, MFCD and HUD keep on getting 'tweaked'? Those displays are something very basic that should have worked from day 1 the pre-release was announced and distributed. I still have a blurry HUD in my main view with my monitor setup. Been like that for months! CANNOT REPRODUCE? There is a problem as shown here. All of those reporting should share their exact monitor setup and monitor config file so ED can better understand our current DCS configuration. ---

What version NUMBER?

What version NUMBER did you see this in?

I previously posted the push function on the left side WH switch is useless. Like you said, it's too easy to select another weapon if your not careful. I just mapped the center press push to another HOTAS button, done with that. ---

I kind of figured that out when I moved the TDC press to another PB, works better after that for sure. ---

I plan on buying a Thrustmaster F/A-18 stick in the future. Anyone that has one, how many positions on that stick? Thanks all, you have been great. ---

Just fixing to start to learn HARM's. So this is real issue question to you experienced folks here. If it's a new bug... just wonderful, its another 'well it used to work' item that is now broken? I guess I will still look at training and learn the HARM anyway I suppose. ---

^^^ Plus one. I built a few Hornet sims for the Navy, this sim sounds are pretty damn accurate.

So this is another issue with the F/A-18C that 'used to work'? Was just starting to learn to use the pod, thanks for the info here. I thought it was something i was doing wrong. It's about as bad as slewing MAV's with the TDC with the TM Warhog. Moved the TDC depress to another HOTAS button. As a fairly new user of DCS and my only module, the F/A-18. It's getting pretty damn old that this particular aircraft is constantly being broken by updates. I have seen 3 different MPCD, DDI readability fixes, something that should have worked since pre-release and it is still not right. The MPCD brightness and day/night modes no longer function. DDI's are much better now. Seems that I spend more time trying to figure out if there is a bug somewhere here and there and looking for answers... than I do actually trying to really learn this aircraft anymore. Sometimes I walk away for a while then come back. Again, thanks for the info. ---

So, no further discussion? Is it a 3-way+push or a 4-way+push in the real jet? BTW: The standard TM Warthog A-10 stick has a 4-way + push. However the push function is of no use. It's to easy to 'hit' one of the up-down-left-right positions while pushing in on the switch and there goes your weapons select and possible radar lock, not good in the middle of a furball. I have mine set to FWD = AIM7, RIGHT = AIM120, AFT = GUN, LEFT = AIM9. Again, the TM switch is a lot less 'firm' getting it into positions than a real F/A-18 stick. ---

Agreed, HMD is too bright at night time even at the lowest setting. ---

[EDIT : just saw this has already been reported, my apology] Currently using 2.5.6.52437 stable. Just noticed when the MPCD is set to DAY mode (upper left rocker switch) the fonts/text get dimmer instead of brighter. Pressing NIGHT the fonts/text get a little brighter. I have the MPCD MAP disabled. And not to mention, the readability of the now very dim DDI and MPCD's during the daytime is making things still difficult to read anyway. A separate issue to be addressed (already discussed in another thread). ===

Overall brightness in the F/A-18C displays and console back-lighting has dropped in the last update, 2.5.6.52437. Went to fly a MP last night and could hardly read the DDI's, much less the MPCD. Also to mention, the DAY and NIGHT function on the MPCD is reversed, day setting is now less bright than the night setting. I joined the DCS crew about 10 months ago after seeing the F/A-18C demo video. I said "damn, I have to have that!". The displays no longer look like the ones in the per-release demo video made by ED. I know they are trying to improve the display quality, in fact the last update fixed the direct sun readability issue, the face of the displays is no longer 'smudged' with finger prints or whatever that was. Nice dark green background which now looks realistic, at least to me and photo's of actual cockpits. Now we are fighting a overall lighting issue, the text/font is very dim - you have to zoom in to see it. I know ED is trying to fix, but one issue gets fixed and then another pops up. It's very aggravating. Two images at the start of the MP attached. The dimmer MPCD image is what happens in DAY mode, it's brighter in NIGHT mode. Same Gamma setting I have been using: ---