Ven

Thanks for confirming it and reporting it as well. While I'm at it I'd like to ask another question too simple to open another thread for. Avenger can't kill T80? I emptied all cannons on one T80 and it's still alive. If not, what can kill T80? Only Mav's? Mk82? 20?

Yes I mean when they are close together but not THAT close together. I slew it onto the target I want but it always snaps back to the other one. As I've said, this is from distance of about 5nm and I finally can get the lock on the target I want when I'm in about 3.5nm but this basically reduces the range for Maverick.

During missions, I set the waypoint to the target waypoint and then switch to A-G mode. This seemed like an easy way to orient myself to the target as the HSI always points to the target waypoint. But I noticed that the distance to waypoint number... both on the HSI and HUD freezes at the point I switched to A-G mode. Doesn't get updated in A-G mode. Is this normal? Also with Mavericks... why is it so difficult to lock the target I want? If multiple vehicles are in a cluster, it always locks onto one of the target and keeps doing it until I'm within 4~3nm. Am I doing something wrong? I am following the procedure in the manual.

I miss the fast battle planner.

Those of you with X52 Pro... you do know you can change SST profile at any time using the clutch button? I have separate profile for each aircraft and switch them during flight if I wanted to. And with SST, I just duplicate the profile, then make minor tweaks for each aircraft. Quicker than setting it all in game profile.

Hmm... usually, visor goes up when the canopy goes up but haven't seen the visor up while keeping the canopy down. Have you tried opening and then closing the canopy?

The numbers in the lower right corner of the HUD indicating the waypoint and distance... I'm not sure if this is bug or actually how it is so apologize in advance for asking. I was using that number to measure distance to the target and noticed that the number doesn't get updated in A-G mode. It seems to be stuck at the point when I switched to A-G mode. Is this the how it's supposed to be?

I think the bands workaround works well. I find no performance difference between setting it as bands or as mouse axis. Sarge's suggestion is an option indeed but I actually like to use the mouse itself rather than mouse stick for external views. But what I have issue with is the mouse wheel zoom. I use the wheel zoom for cockpit (F1) view zooming as well as external view zoom. And in cockpit, my natural instinct is to roll the wheel forward (away from me) for zoom in and towards me for zoom out. And this works fine but for external view, it's backward. I naturally roll the wheel backward for zoom out but it's actually zoom in. If I invert this in the options, the cockpit gets inversed too. It's not a big issue as I don't use external views often but I hope there is a workaround to this.

Been playing around with the value below that line trying to minimize the effect rather than turning it off. Although I never was a pilot, I believe you're supposed to keep your head straight during turns so the effect seems unrealistic but having the head perfectly straight as if your head is nailed to the cockpit also seemed unrealistic. I'm at work now so I don't have the exact value but lowering the value just below that line from 45 to 10 seemed to reduce the amount of rolling effect. And then lowering the value below that from 0.5 to 0.2 seems to make the rolling quicker so it doesn't seem like I'm in a boat. So by playing with those two values, I have the head fairly straight with a slight rolling effect which I like.

The mouse stick is basically duplicate of the.... mouse. You gotta set the mouse axis to the TDS Slew. The problem is, mouse wont work for external view rotation anymore... if you're planning to use external views, you would have problem. What I ended up doing was set the mouse stick as bands in profiler and assigned the slew keys to them. Works just as well.

I think the problem was all these planning. Besides the quality, the voice sounds very uninteresting and scripted... probably because they were scripted. More casual trainings would've been more effective such as Ironhand's tutorials. Anyone know if he's planning to make more training videos for FC2.0?

I hope this is not the "higher" quality version they were talking about. Did ED record the voice in the bathroom? Can't understand half of what he's saying.

Good to know I'm not the only one having difficulty identifying targets. Very good read.

Is there way to minimize this effect instead of completely turning it off? There are some numbers below that head_roll_shaking which seems to be related but haven't really tested those.

I never compared side by side but some have changed. Rate of fire for A10 is gone, some radar mode select seems to be different from what I can remember. But for the most part, they seems to be similar. You should only be making minor tweaks but I suggest flying with your current profile and make changes as you discover them.

Install LO at its default directory. Install FC 2.0 at its default directory. (no need to install any patches or FC 1.1) Then to save disc space, uninstall LO unless you're planning to play that version.

I was wondering about that before I installed. But I installed the original LockOn from the CD and then installed the FC2.0. Didn't apply FC1.1 or any patch. Then uninstalled the LockOn.

That youtube video is quite amazing. It's not shot on the surface of water but still... how the cannon rounds shot downward can ricochet up is very interesting effect? I was hoping that someone would explain that in a logical and scientific way. No more "rock skipping" explanation.

Seems to run smoother for me. 1.1, I had to make cfg tweaks and tweak mods to make it run smooth. 2.0 seems to be as smooth as the modded 1.1 right out of the box.

Again, I'm aware of the projectiles bouncing off water and soft objects at shallow angle. In this example I'm sure you didn't shoot down at the water. But was wondering how a 30mm cannon shooting down at surface of the water can bounce off. I originally assumed that this was just overlooked in the sim as it may be too much work to implement this in all the rivers and lakes in the game. But some of you are saying that this is realistic so I was curious if anyone had some logical explanation. Not another example of shallow ricochet.

Of course at shallow angle. But 30mm cannon rounds bouncing off surface of water at 40 degree angle is a bit different than skipping rocks.

It's not that I'm doubting anyone but just curious. Is there any scientific explanation for this?

I just downloaded the game last night so haven't played much but in the F15 Quick start mission, I can see the flame of the plane I shot down through the clouds. As if the flame is above the cloud. Minor but annoying.

I actually prefer the video training than the tracks in DCS since I can fast forward, and rewind with videos. And don't necessarily have to launch the game to watch it. Why I liked the Ironhand's tutorials. But I would have to agree that the video compression and resolution could have been a bit better. Perhaps an MP4 version with a bit higher resolution that we can download would be great.

Still not clear. 1. What exactly is "lasing"? Locking a target with laser rangefinder or just turning on the laser rangefinder? 2. Regardless, that means I basically shouldn't have it on for more than 10 seconds at a time? And that also means each series is about 2 and a half minutes? 3. When designating targets for Datalink, I keep it on, lock target, send to Datalink, move on to next target, and repeat for 3 ~ 5 targets at a time. I just cannot do this in 10 seconds. Do I have to turn it off every 10 seconds and wait 5 seconds? I tried locking the target first and then turning on the LRF, this doesn't seem to work.