Chops

It's not to early to call it an issue, and it definitely needs tweaking. Myself and others have commented on the flight model and thrust/drag, FCS interaction since the early access Hornet was released. Eagle Dynamics is currently looking into these problems.

I can also confirm that the FCS Bit will not complete after a full shutdown of the aircraft, and a restart. Seems that this is definitely a bug.

Thanks for the Checklist. Pattern Entry should be at 350 kts if you are pulling 3.5 g's in the break.

Here is my explanation of the FCS Bit Test from another Thread, go to Post #4: https://forums.eagle.ru/showthread.php?t=211493

I tested this procedure and found the same problem during start-up, however, it was due to pilot error. I realized that I left NWS steering on. See the following note from the NATOPS Manual - Pg. 243 NOTE • For initiated BIT to start, FCS BIT consent switch must be held for at least 2 seconds. If not held for the required time, RESTRT is displayed as the BIT display status message. If RESTRT displayed, repeat procedure. • Initiated FCS BIT cannot be performed if nosewheel steering is engaged. • For valid BIT reporting, do not operate switches or controls unless indicated. Do not rest feet on rudder pedals or hands on control stick. 1. If wings folded, check both ailerons Xd out. Here are the key bindings that I assigned in Control Options - FCS Reset Button (Left Console) – B key FCS Bit Switch (Right Vertical Panel) – Y key Paddle Switch (Control Stick), this is called Autopilot/Nosewheel Steering Disengage (Paddle) Switch in the DCS Control Options – A key I followed the NATOPS checklist as follows and successfully completed the test: Page 324 5. FCS RESET button – PUSH Press B key If the wings are folded, verify aileron Xs are present 6. FLAP switch – AUTO 7. FCS RESET button and paddle switch - ACTUATE SIMULTANEOUSLY Press B key and A key at the same time If nosewheel steering (NWS) is engaged the following FCS Bit test won’t work properly. Make sure NWS is no longer displayed on the Heads Up Display (HUD) 8. FLAP switch – HALF 9. FCS INITIATED BIT – PERFORM Press Y key for 2 seconds, continue to hold and press the FCS-MC > FCS OBS button on the right DDI at the same time until you see IN TEST displayed on DDI then release both key presses. a. AOA warning tone - VERIFY ANNUNCIATION AT FCS IBIT COMPLETION

I used the Kneeboard Bulder program (the website is listed a few posts up) to install custom checklist files including the Quick Start Manual to the kneeboard. The program works great, however, the resolution of the kneeboard files is not very readable. What is the recommended DPI in order to get clear text on the kneeboard?

I have a few questions regarding the checklist steps you mentioned, and will try to replicate the issue. Pg. 324 5. FCS RESET button - PUSH If the wings are folded, verify aileron Xs are present. Pg. 325 6. FLAP switch - AUTO 7. FCS RESET button and paddle switch - ACTUATE SIMULTANEOUSLY (what is the key command for the Paddle Switch?) 8. FLAP switch - HALF 9. FCS INITIATED BIT - PERFORM (Is this check completed by pressing FCS-MC > FCS on DDI and Y key command - FCS Bit switch simultaneously?) a. AOA warning tone - VERIFY ANNUNCIATION AT FCS IBIT COMPLETION

For Auto Throttle (ATC) press and hold the T key. You should see ATC displayed on the Heads Up Display (HUD).

Prior to INS Alignment, the Lat Long Coordinates shown on the Persian Gulf F10 Map view for my aircraft don't match what is shown in the cockpit for Waypoint 0. See the attached screenshots:

Matt, can you please share your thoughts on the flight model, and the comments made in the video? Are the developers aware of these issues? The Carrier landings and pattern work shown in your early access training videos are quite impressive, especially given the state of the early access flight model.

Thank you very much for your video and comments regarding the flight model. Although I have not flown the F/A-18C, I have flown a number of different aircraft including single-engine pistons, multi-engine turboprops, and multi-engine jets as a professional pilot. I immediately recognized the same problems you mentioned in the video after flying the DCS Hornet for a few minutes. It is just not how a real jet aircraft behaves. I am hopeful and confident that the developers will look into the issues with the flight model, thrust, and airspeed behavior.

Is there a realistic time period in which the following DCS Aircraft would have been involved in a conflict at the same time? F-5E A-10C F/A-18C F-14 A/B AV-8B N/A AJS-37

Enter the A-10C cockpit. Look at the left MFD and choose Stat. Click Next. Use the arrow button to scroll down to Throttle. Choose the number 9 on UFC and then click on slew on the MFD screen, to replace the existing number.

I searched the Forums for information on how to move the Pilot on the ground, but did not find any information. My apologies if this has been answered elsewhere, but is there a list of key commands for controlling the pilot on the ground after ejecting, or a way to move the pilot around the aircraft during pre-flight to get a close look at the aircraft exterior?

You are correct. I just set up another test scenario and changed the time of day from 7am to 10am, and I was able to use the TGP to track a moving vehicle.

Thank you, the problem just seems to be with the Normandy Map.

Guys, thank you. However, my problem is that I can't get the TGP to lock onto and track a moving target. Therefore, I can't make it SPI and slave weapons to the moving target. Shouldn't the TGP be able to track a moving target in Point mode?

I am unable to get the TGP to lock onto and track a moving ground target on the Normandy map. I have tried locking onto the target using Point mode. Is anyone else experiencing this problem?

I encountered the same problem. I had previously moved Normandy and NTTR over from my OpenAlpha install after updating to 2.5. I ran update and repair. The updater recognized NTTR but not Normandy, which prompted me to search around in the Module Manager. Within the Module Manager, it showed that I had a valid install and serial number. I clicked on the DRM button and looked around in the activation window, but did not re-activate. When I closed it out I saw an option to install Normandy. I clicked on the link that said install and the updater started downloading about 4GB of data.

I have the OpenAlpha installed on the same hard drive as my 1.5 OpenBeta, however, the 2.5 installation program is not seeing my OpenAlpha install (Normandy, NTTR) and is trying to download everything. I used the .txt file listed above, using the appropriate directories for my install, but it is still not seeing my OpenAlpha install. S:\\Eagle Dynamics\\DCS World 2 OpenAlpha Any other suggestions?

Can you please explain this? I have no idea what you are talking about.

Does anyone know why there has been such a substantial increase in cost for the GTX 1080 Ti? At the end of December the cost was around $760 u.s. and is now up to around $1,400 u.s.

The Radar Cursor won't work for me in 1.5xxx Open Beta however it does work in 2.1xx Alpha (Nevada)

Nicholas, I posted a bug report in the Viggen Bugs and Problems Forum on December 4th. No one has responded to my post. I have not idea if the problem is something that I am doing wrong, or if it is in fact a bug. What is the process for getting help? Your Bug reporting system does not seem to be working very well.

Matt (Wags) posted the following information back in April 2014 along with a module matrix document. Are there any updates to this information? There have been a number of module releases since 2014. Is a current module matrix document available? "The below is provided to explain the various fidelity levels of flight dynamics and cockpit systems modeling available in our various DCS aircraft simulation products. We provide this to you to help better understand what your are purchasing: Standard Flight Model (SFM). This has not changed and defines a more data-driven means of achieving flight dynamics, in conjunction with some scripting. SFM was used in the Lock On series and is still used in the Flaming Cliffs 3 Su-33 and MiG-29. However, we do plan to update these at a later time. Advanced Flight Model (AFM) and AFM+. An AFM uses multiple points of force application and calculation on the relevant flight surfaces. This simulates edge of envelope conditions well and avoids scripted behaviors as used in an SFM. This system also partially implements the aircraft's flight augmentation systems. DCS aircraft that use AFM includes the Su-25T. A further evolution of the AFM is what we term the AFM+ and this uses the same calculations as AFM but adds limited modeling of the hydraulic and fuel systems. Examples of AFM+ in DCS include the Su-25 and A-10A. Professional Flight Model (PFM). This is generations beyond an AFM/AFM+ and is based upon: • Use a wider array of wind tunnel tests CFD methods for aerodynamics parameters calculations. • A higher level of aircraft construction details for forces calculations. For example: our landing gear model includes individual kinematics of retracting/extending is used to calculate its movement, servo-piston forces, etc. In such cases, we truly use real lengths, arms, etc. This also includes such items as a realistic simulation of airflow along the airframe due to the propeller or helicopter rotor thrust. • Realistic simulation of Flight Control, CAS and Autopilot systems. • Realistic simulation of Hydraulics, Fuel, Electrical, Engine and other systems influence flight characteristics. • Unprecedented access to test data packs. This is combined with much more detailed and accurate accounting of the physical forces on the aircraft and airfoils. DCS examples of the PFM include the A-10C, Ka-50, P-51D, UH-1H, Mi-8MTV2, F-15C and Su-27 (in development) for DCS Flaming Cliffs, and the Fw190-D9 (in development). External Flight Model (EFM). Used by our partner developers, the EFM uses only a part of PFM - rigid body physics and contact model. What forces and moments are applied to this rigid body from aerodynamics and any other sources except the contact forces is up to EFM developer. Standard Systems Modeling (SSM). A DCS module using SSM is characterized as including just the most essential cockpit systems and using keyboard and joystick commands only to interact with the cockpit. Examples of SSM in DCS include all of the Flaming Cliffs 3 aircraft. Advanced Systems Modeling (ASM). An ASM enabled aircraft goes into great depth to model the intricacies of the various cockpit systems, to include functionality for almost all the buttons, switches, dials, etc. A key element of an ASM cockpit is the ability to interact with it using your mouse. ASM DCS examples include the A-10C, Ka-50, P-51D, UH-1H and Mi-8MTV2. In the coming weeks, we will be updating our store pages to use these product definitions."