lennycutler

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

This happened to me 3 times, when I locked on to a target....this was after I had adjusted my axis curves for the TDC to around 15 saturation....after I changed to saturation to 25 the problem stopped....so far. Perhaps your issue is also impacted by the axis curve settings for the TDC?

I just recently regained access to my DCS BS2 KA-50 modules, after my activation got messed up. Had to re-install everything. Now I can fly KA-50, in DCS World but when I try to install the training video file...I get an error message which states "Can't Find DCS - Installation Interupted" I have tried this several times placing the training installation exe file in my root directory, and in the DCS root directory...same error occurs. What may I be doing wrong here....of course worse come to worse, I still can use my StandAlone BS2 training...since I have not yet deleted standalone BS2.

After two days of trying various methods to get my BS2 DCS upgrade module to work in DCS World...I found something that worked. 1. I deleted my DCS World KA-50 folder. 2. I ran my original KA-50 standalone, entered a mission, when prompted for a serial number I entered that, got the activation. 3. Ran the BS2 Upgrade Module for DCS World. 4. Did a DCS World Update. Now the only thing I am still trying to get to work is the KA-50 training videos, which I have downloaded twice, and could not install...getting the error message..."can't find DCS World"

I had to re-install DCS world today, because my start menu for Eagle Dynamics got messed up after I uninstalled standalone BS2. I had to re-install it to get DCS world to let me use BS2 again. In the process, the AutoUpdate stopped working. The log shows this "00000.000 INFO : === MiniLog opened UTC 2012-10-27 20:48:26 00000.003 ERROR : Caught an exception: parse_config("E:\Program Files\Eagle Dynamics\DCS World\autoupdate.cfg"): JSON error: parse error: premature EOF (right here) ------^ 00004.700 INFO : LAUNCH found 1 commands 00004.705 INFO : LAUNCH started "E:\Program Files\Eagle Dynamics\DCS World\bin/Launcher.exe" 00004.705 INFO : === MiniLog closed. Update: I looked in the root directory for DCS World...and found the autoupdate.cfg file...mine was empty. I copied over the file with a recent backup I had stored on an external drive...Now the update works...However, now my BS2 won't work...as part of DCS Modules...even though the correct serial number is shown...and DCS World says my hardware code is wrong...but nothing has changed on my machine....I did send an email to Eagle Dynamics asking for an activation code...don't know why BS2 continues to not work here...all my other mods P51, A10 work in DCS world. What can I do to fix this?

The controls for cockpit view to lower the pilots view (eye position) is Rshift plus R-control Plus Num 2. I have TrackIR. When I try to lower my cockpit viewpoint to better see the aiming recticle, I suspend trackIR then use the R-Ctrl, R-Shift, Num 2 key combination. I observe my eyepoint being lowered. Then I try to save this new position by using R-Alt Num 0, which should save this view for future missions etc. But when I re-engage TrackIR, my cockpit eye viewpoint reverts to the original default setting. How can I change the cockpit view so that it is not reverting back to the default? I could not find an answer to this issue in prior posts.

In version 1.2.1.6148 - now that I have checked my axis settings, and using invert....the action of the rudder trim looks correct.....maybe it was right all along?

Rudder Trim Wheel Arrow Markings I agree, when setting the rudder tab to the right, the tab will actually move to the left. However, to check my issue with the labeling of the arrow directions on the rudder trim tab wheel, I took some pictures of the A2A P-51. You can see that it has the correct arrow direction on the trim wheel for the rudder trim, as compared to DCS P-51. Also is a picture of the A2A P 51 showing the rear view of the aircraft reflecting the correct position of the rudder tab when set 5 degrees right. I think ED needs to confirm and or correct the labeling of the arrow directions (left vs right) on its model of DCS P-51D.

When applying 5-6 degrees right trim on the rudder, I have to move the rudder trim wheel counter clockwise. Viewing the trim tab from the outside aircraft view confirms the rudder trim tab moves slightly to the right. But the arrows on the rudder trim wheel indicates that moving the wheel counter clockwise applies left rudder trim. Seems to me, this is just cosmetic...but it had me confused, I was putting the trim to the left since the left arrow which indicates move the wheel clockwise, was moving the trim tab left instead of right. So, unless I am still totally confused...seems that the arrows on the rudder trim wheel need to be corrected to reflect the correct direction for right and left trim rudder.

I have mapped my Hotas Warthog Throttle slider as an axis for the rudder trim. I noticed (see pictures attached) that when on the ground ready for takeoff and while in the air, when all indications from cockpit instruments reflect that the aircraft is at zero rudder deflection, the rudder trim dial is not actually positioned in the zero position. But is positioned around 1 or 2 degrees. When observing from the ready for takeoff postion, from the rear of the aircraft, it appears that the rudder trim, visually from the rear view is at a zero degree position. I am not sure if this is actually impacting flight characteristics or just cosmetic. I checked my axis settings for rudder trim and they reflect that the slider is positioned correctly at a neutral position when the Hotas Warthog throttle slider is at the center detent. Hopefully others can confirm through observation of their own rudder trim dial positions if this is just happening to me...or is it a actual bug....or just cosmetic.

I imported my old p-51D mappings. For example of issues - the War Emergency Power is new....and mapped by default to the 'E' key. If I want to also map it to a throttle button, I can't...I don't know if it is intended to be blocked from mapping to other than a keyboard key...but even though I really don't need to make the change...if I wanted to fix this...so I could map it...how can I fix this via the options menu or manually via a lua edit?. And assuming I have other issues or bugs do to my import of the old lua file...what is the suggested way to fix it?

I created a routine SEAD mission for the SU 25T. Targets were a M48 Chapparrel and one Hawk battery. Using the standard SEAD missiles I was routinely successful at knocking out the Hawks...but the M48 Chapparrel never provide an indication via the ETS... Is there something unique about the M48 that prevents the ETS from picking up its signal. It successfully launched its missiles....are they IR only...launched without the use of RADAR? I am using the IR Jammer to help survive.

Bombers Not Showing Up Thanks for the quick response...yes I changed it to have multiple groups - each group has one plane...and of course it works.

When I create a mission with the P51 to intercept bombers - only one bomber shows up in the mission when it runs...while there are more than one created in the mission editor. The mission summary correctly reflects the number of bombers...but only one enemy bomber shows up when I run it. See attached example. Is this a known Bug. beta 120 protect carrier.miz

Cockpit Shadows on High Shadow Settings I just tried it again with high shadows settings. See attached pictures.

resolution set to 256. I thought this settings impacts things like mirrors, MFDs, but not shadows?

I can't seem to get rid of the Zig Zag lines in the cockpit shadows. I tried changing various graphic shadow and anti-aliasing settings - but the step ladder shadow lines are still their. I have an Nvidia 460 with the latest drivers. Any suggestions...see the picture I have included.

I would like ED to tell us what new settings exist for input commands for BS and A-10, so that those of us, who choose to import, copy the settings, can then quickly determine what is different in the current DCS world...and we can make the changes more efficiently, rather than the more time consuming process, of re-mapping a lot of keys strokes etc.

I may not have done it right...1. first I downloaded the DCS world update. Then I downloaded the A-10 update. When I installed, the P-51D was not in DCS world. So, I re-installed the P-51D latest beta version. Then when I tried the A-10 I noticed my controller profiles were not automatically ported over. I found them in their original directory from the A-10 standalone install and copied them over to the DCS world appropriate input folder. Now everything is working. So...was the updated install supposed to automatically find the controller input files automatically for A-10 - if so it did not happen in my case. If not automatic - then there were no instructions provided to manually copy the files to the proper folder in DCS world.

I agree, while the P-51D Beta is outstanding, a real challenge and joy to fly, ROF, which I have been flying for many months is immersive to the extreme. It's combination of great graphics, flight dynamics, improved user interface, modelled physics and a customer focus regarding enhancements is rare.

The new patch had no impact on my Hotas Warthog and CH Rudder settings.

Thanks, just finished downloading the files via FTP....thanks for your help.

A2A P-40 Bought it two days ago and I am having a ball learning how to manage the engines, and handle the hydraulics. I would like to get some checklist information - for example, seems like when taking off you set the fuel indicator to Aux, then switch to fuselage.... but documentation does not speak about switching to the other tanks. No much info on how and when to put the propeller into the correct manual mode. I am trying to re-read all the provided docs and anything else I can pick up on the Internet.