malibu43

Ya, but IRL they would clear trees if they were that close to being in the glide path. If something goes wrong on final or your nursing a damaged plane in, that tree is in a bad spot. You may be right about it not being in glide path, but it's presence there was enough for me to stop and think "that's odd...". That's not good for immersion.

Found this guy in the first mission of the A-10A The Valley campaign.

I would think some chainsaws are in order...

Agree. This looks really bad... Can it be removed?

Installing previous driver fixed it!

I thought that was it too after reading the crash log, but it didn't fix it... Should I try a different driver...?

Deleting the options.lua file did not work. Please advise next steps.

Ok. I will try that. However, I believe I completely deleted my saved games folder after the last uninstallation.

I upgraded to 2.5 from 1.5 release and had this issue. Unistalled and reinstalled using the 2.5 stand alone and have the same issue. Game installs fine. But the first time I run it, it asks for login, I enter it and click sign in, and then I get a crash. I ran the repair tool when I got the crashes after trying to go from 1.5 to 2.5 and it didn't help. I have not tried repairing since using the standalone 2.5 installer. Please help! Screenshot and crash log attached. dcs.log-20180201-141136.zip

+1 Please implement this for the release of the F-18C.

Thanks for that. I'll take a look at it later. I played through the first campaign mission twice last night and still couldn't figure out how the ILS/HSI/Steering Cues were trying to get me lined up with the runway. I'm not trying a zero vis landing, but there is quite a bit of fog. It's the first campaign mission, so I'm assuming they are conditions that I should be able to land in. Once I'm on short final, I can see enough. But getting to on a stable, aligned final approach is really what is giving me a hard time at this point. I can't seem to find any instruments that will get me there.

Thanks. That makes me feel a little better.

Thanks. That helps a bit. Once I'm in ILS mode and have the correct airfield selected (by cycling waypoints, right?), at what point should I get the ILS bars/lines on my HUD. I thought I had everything set up for the airfield I was at, but I never got the ILS bars. Just that little flight director cross.

I played through the first incredibly boring campaign mission for the F-15C last night, just to over shoot the runway and crash at the end. How does the ILS work in the FC3 aircraft, specifically the F-15C? Should it automatically come up if I'm in Nav mode on the HUD and the waypoint selected is an airport? Or 1) is there something specific I have to do to display the ILS in the HUD, and 2) do I have to do something to tune it to the airport I'm landing at? I've looked through the manual but can't find any info on it.

Thanks for all the insight guys. Definitely makes more sense now. I guess I'll have to make some pre-mission decisions if I want the ability to do ad-hoc pop-up attacks with CBU-87s or be limited to CCRP with the more lethal CBU-97.

I was using the bombs and mavericks training mission to investigate the CBU-97 CCIP issue last night, and noticed that CBU-87's still land well short of the where the piper is when used in CCIP mode. I thought I remember reading that this was fixed in one of the change logs...?

Yeah. I think now that's what I was seeing also. Thanks for recreating it and getting it on video!

I am glad I just found this thread. I see that some of the issues I'm experiencing aren't just me. I have posted another issue I just discovered last night regarding CBU-97s and CCIP/CCRP: http://forums.eagle.ru/showthread.php?t=122103 I am a bit frustrated that over a year after purchasing FC3, I am still surprised and confused by these kinds of issues every time I try to fly.

I recently fired up FC3 after not having played in a while. It took a few minutes of confusion/frustration before I realized that CBU-97's were only working in CCRP mode. Trying to use them in CCIP mode resulted in some weirdness on the HUD. I loaded up with Mk82's and was able to switch between and use CCIP and CCRP just fine. Tried CBU-97s again and still wasn't able to use CCIP. Is this "as intended" or a bug?

I'm playing (very slowly) through the The Valley campaign, and on mission 3, I noticed that the waypoints shown in the briefing don't match the waypoints in the actual mission. The briefing has waypoints 4 and 5 as "Attack" waypoints, and has 4 to the North-West of 5. The waypoints during the mission have 5 and 6 as the Attack waypoints, and 5 is to the South-East of 6. I'm going off of memory, so the exact numbers may be incorrect, but I know that during the mission there is one extra waypoint during ingress and that I attack from the opposite direction shown during the briefing. I've the played the mission a couple of times and have yet to successfully find the targets, and I'm wondering if the briefing/mission mismatch has something to do with it. I am patched up to the current version. I did start the campaign before the last patch (if the helps at all). Thanks.

I personally don't think "buy a better computer" is the appropriate solution for the issue being discussed in this thread. It is one possible solution, but I don't think its the right one. It would not be a wise business decision for ED to simply expect their customers to upgrade their computers every time they degrade performance for no apparent reason.

That explains that. Thanks!!!!

I had my first go with the mission editor to try and create a simple A2A practice mission for the FC3 F-15C. I set up my aircraft head out over the ocean near Batumi with just the starting point and one waypoint out a ways over the water. I created a flight IL-78's that start ahead of me and to my right that cross my path and then kind of turn around and head back toward the North. In the "unit" section for the IL-78 flight, I have the "of" field set to 4, however, when I fly the mission I only get one enemy aircraft. Am I missing something? I can post the mission later if that helps.

Good point. :D HP Pavillion Dv6t Quad Edition, Win7 (64), i7 2.0ghz (2.9ghz w/ Turbo Boost), 1GB Radeon HD6770M, 6GB RAM, 640GB HD FWIW, I'm not necessarily looking for help at this point. More or less trying to bring the issue to light, specifically the fact that the auto update process seems to have caused some hiccups. Although, ideally you could expect similar performance from module to module as well. The performance I'm getting may just be all I can expect on a laptop, and I understand that.

After much tuning, tweaking, and testing, I got my FPS in FC3 to stable 25-30 with good visuals (in the 6dof pits). I bought the Huey and noticed it was down in the 15-17 range in the cockpit. I thought maybe this was something just related to the Huey and its clickable pit. However, I then went back to the A-10A and found that my fps was down in the 15-17 range there as well. My installation history at that point was probably something like: 1. DCS World (whatever first version to allow auto updates) 2. Some updates (I think) 3. FC3 installed in January 4. Some more updates 5. DCS Huey installed last week I uninstalled DCS world and then reinstalled as follows: 1. DCS World (current version) 2. FC3 (current version) 3. DCS Huey (current version) When I went back into the game, my FC3/SU-25T fps were back up in the high 20's and low 30's, and my fps in the Huey were more in the 17-20 range. I'm happy with my performance now but the two things I wanted to highlight for the devs are: 1. For some reason the installation order I had the first time gave me some fps issues, even though I don't think it should have. 2. DCS Huey gives me substantially lower fps than the FC3 aircraft (even in external views). I don't have A-10C or KA-50, so I don't know if that's normal (due to clickable pits or something), or if it's a Huey/beta thing.