lennycutler

I tried the auto update...It said it was successful...but...all of my modules were not updated...in fact DCS would not let me fly first person in most of my mods (BS2, A-10C, P-51D)...and reflected on the Spash page that all of my Mods, including FC3 were the prior version. I downloaded all the Torrent files for all of my mods. I installed each one. I got activation errors on FC3...insisted I needed Lock On...which I thought I had already installed....and BS1...which I thought previously I was safe to uninstall. So. I installed Lock On again...I installed BS1 again...and had to manually activate it. Finally, almost got everything working except for BS2...which did not accept my serial number. I did the registry delete for BS2 activation, per the Forum...then redownloaded BS2 using the upgrade International Key...and thank God...it all worked. Now here is my Beef...Dear ED.....I thought the AutoUpdater would not fail again to screw up my system....but it put me through 2 hours of extra work. Please ED, Fix the autoupdater....or just plain tell us not to use it for any major update....and please give us the proper procedure to make sure that all of our Mods come back to life.. Question - When is it ever going to be safe to delete the BS1 file?...and I assume it will never be safe to delete Lock On folder. I frankly don't mind a complete re-install...but the re-activation process is mind numbing. What is the proper procedure to ensure that everything I already own...comes back to life updated without me having to get re-activation problems - (e.g. - serial number not recognized, no hardware code etc.) Sorry for the rant...but this is the most frustrating part of working with this excellent software.

Strange AI behaviour SU-34 In the attached simple mission my F-15C attempts to engage a SU-34 armed with bombs and air-air weapons. When the SU-34 detects my missile launch it makes an abrupt manuver and dives into the ground. It did this when its flight alt was low, so I raised the alt to a few thousand feet. The AI is set to Expert - It would appear that the AI behavior is a bug- appreciate if someone from ED Testers group can check this out. F15C VS SU34 AIM 9.miz

Thanks, I tried the repair option..but the R-27EM is still available....should I re-install DCS world and FC3....and does the saved games folder have an impact on this happening?...I never delete it...since I update via the auto updater. UPDATE: Re-Install DCS World only, not the Mods....and retained all folders in Saved Games. This solved the problem.

For me, this only occurs when selecting a payload for the SU-33, when the SU-33 is an AI aircraft.

See attached pictures from the SU-33 Payload Screen for CAP missions...note I edited the name of the payload, not the payload.

SU-33 Loadout Causes CTD in FC3 I recently reported this problem related to one particuliar SU-33 CAP loadout, which caused my F-15C mission to CTD. Now I have determined that this also occurs with this one SU-33 loadout when opposed to player in a Mig-29. The crash occurs once you enter BVR mode, even without turning the RADAR on. I have attached a screen print of the loadout, a crash log and the mission file. I hope this gets investigated for potential inclusion in the bugs to be resolved list. NOTE: Testing this further is seems to be cuased by the R-27EM Missile in the selected loadout. Perhaps ED can confirm if the R-27EM is supposed to be in any loadouts, or is it in this one in error? DCS-20130319-133905.txt test Mig29s vs SU 33.miz

F15-C Crashes when Engaging SU-33 When SU-33 Load has the following See attached mission file and crash log....this crash happens only when the SU-33 (bandit) has the weapons load in the CAP mission. I tried all the other CAP loads with no crashes. The crash occurs when you go into BVR mode and then turn on the Radar. I am including the mission file and the cash log. I am using the modded SU-33, but the same crash occurs with or without it...so somehow I think it is linked to the F-15 Radar interplay with the SU-33 load, ECM etc. test su33 crash error w f15c.miz DCS-20130318-012400.txt

Ver 1.2.3 did not fix the TU-95 LOD bug...so I am using Mustangs LOD fix from November 2012....by just extracting the LOD file for the TU-95 from it, and putting in the appropriate Ver. 1.2.3 folder. I wonder what other LOD errors still exist in Ver. 1.2.3

Updated mission see attached....this is not currently set up for battle field commander...but you can easily do that.... It now seems to work well....getting SAMs to engage etc. Test Hawk Battery Engagement.miz

Thanks Grimes for the quick feedback.

Corrected SAM Placement In the attached corrected mission file...I have correctly assigned the SAM components to their respective groups. Both the Hawks and Patriots successfully engaged the attacking SU 25Ts etc. It also may be needed that the Patriot AN-53 has it's motor facing away from the target area, but I am not sure if that is needed. Not sure, but I believe you need one AN 104 for each Patriot launcher, and I also put in the ICC unit for the Patriot, not sure if that is required. Wonder if there is any documentation as to the essential layout required for Patriots. Test Hawk Battery Engagement.miz

Yes, I have it now...trick is to create the group, populate it with at least one part of the SAM battery....then replace each component to make sure you have the right number of launchers, radar etc...and with the Patriot, you may have to position the AN 53 with its motor facing away from the target area.

I am a bit frustrated. I set up a mission attached, where a Hawk and Patriot Battery, properly equipped, don't seem to want to engage attacking aircraft. After reading this forum, I made sure the batteries were aligned and complete...as far as I know. They just don't come alive, and get attacked by 4 SU 25-Ts. Can someone take a look, and let me know what I am doing wrong? Test Hawk Battery Engagement.miz

Thanks, I will give it a go.

Still No Joy Yes, I tried that and my Hawk Battery did nothing. I have attached the mission file, perhaps there is something else I need to do. T-90 target Patriot Battery.miz

I know I can't control SAM batteries like Hawk and Patriot, but how can I ensure that they engage targets. In my test missions, they just sit there and do nothing while an enemy bomber flies by.

Got it working now...all three orig files that were in the Temp Textures directory, now moved and not renamed to the TempTextures directory. I now have the Nav Lights mapped to my Throttle Pinky Switch. Yes, Halo effect seems a bit too much.

I put the textures into the TempTextures folder. The White and Red lights were then visible but not the green. I did not rename them. PS. How do you turn the lights on when you are the Pilot?

Perhaps I don't understand your issue....for my F15C setup, the display zoom in and out "- and + " keys are mapped to my Warthog Throttle, which increases or decreases the displayed range of the radar. Pressing the keys "[" and "]" has no function. I believe the "+" and "-" keys are the default for display zoom in and out for all flyables in FC3.

In the attached pictures two IL 76's have been hit by 30mm cannons from an A-10C. Notice that parts of the plane are hanging in the air. The plane is on fire...but no explosion. The parts hanging in the air are more critical as an issue.

I have attached a couple of pictures, showing the AIM 9 on the A-10C, in one picture from an external F2 View the Aim-9 looks solid...the next picture (on the right) in the same F2 View it appears semi-transparent. I could not see that this is a known bug from reviewing prior posts.

Let me make sure I understand this. I have now removed Lock On, and Flaming Ciffs standalone....as I understand I will not need them on my system since I now have installed FC3 into DCS world. If I remove Black Shark standalone, and BS 2 Upgrade standalone, - it is my understanding that since I have BS2 upgrade now installed in DCS world, I will not have to keep any of the BS standalone products on my hard drive. Is that understanding correct? Of course I understand that if for some reason I ever have to uninstall DCS world and re-install all of its modules, I will then have to put Lock On back on my system, BS and BS 2 Upgrade back on.....but that process should not be needed since I will use auto updates. Am I correct in this assumption?

Sounds like a simple question, but I want to avoid and further activation issues. I now have the BS2 Updgrade and FC3 modules in DCS World...and so far all is fine with my install modules. When is it safe to uninstall BS2 upgrade standalone - which also has a related BS install standalone....and when can I safely uninstall FC2, and do I have to leave the standalone Lockon on my hard drive for evermore to keep running FC3 in DCS world without problems?

TU-95 LOD Bug I reported this problem in the FC3 bug thread, but since it didn't make the bug list there perhaps it is a DCS World Bug and belongs here. When intercepting TU-95, it is visible beyond 10 miles, but disappears around 5 miles out, only to re-appear again a bit closer. So, no transition from a small LOD to the full visible model...but a jump from small LOD - to- invisible - to detailed LOD. Surely, this appears to be an LOD bug...for at least the TU-95

LOD Bug TU-95 I have attached a track of a simple FC3-intercept of a TU-95 by an F-15C. As you watch the track, observe the TU-95, which remains visible as a small rectangle until the F-15 closes within around 10-15 miles. At that point the TU-95 disappears although it is still lock in on the radar screen, even at the point that I launch the first missile, the TU-95 stays invisible, then at around 8 miles, it suddenly shows up with vivid detail.... So, no transition from a small LOD to the full visible model...but a jump from small LOD - to- invisible - to detailed LOD. Surely, this appears to be an LOD bug...for at least the TU-95 f15c vs TU95 LOD BUG.trk