betatrash

Nope, I can confirm it is still technically beta... The module is beyond busted. Autopilot and Trimmers are beyond repair, and that's just the flight controls... Thread: https://forums.eagle.ru/topic/221282-bugs-fc3-autopilot-trimmer-control-issues Wish ED would make a statement on FC3, or it seems it's never getting fixed. 2014, bruh... "In new beta update manual trim and t/o trim may not work. It's known issue. Please, do not make new topics" 2021, bruh... Still in beta...

FPS dropping from 60 to 40 or from 40 to 25-30 with a single active IR TV display (A-10A). Otherwise FPS remains 40-60. Option request: Update MFCDs and TVs every 1-10 frames instead of every frame, independent of cockpit setting. Though, it's NOT set to update every frame, using 512px textures only. 6 updates per second would be sufficient. Strictly not a bug, but I didn't want to file it as a 'suggestion' due to the large hit to performance on lower end systems. Another option NOT to render (skip) textures in MFCD and TV views may also increase performance. They're not strictly necessary as long as land, water and mountains appear in distinct shades. Although, that would require a filter or shader, to render them as such. Otherwise, they would appear white. Some sort of optimization seems in order here...

When panning the mouse view across the screen, motion is not smooth and consistent. It slows down severely over various elements of the canopy, panels and fuselage, or while moving the mouse at a slow rate of speed. This is extremely annoying, and makes mouse view nearly unusable. v2.5.6.61527 occurs with all FC3 aircraft. Not sure when this bug was introduced, but it didn't previously exist. Have not tested A-10C module. Was planning on picking up F/A-18C module, but you keep breaking things... FC3 Autopilot + Trimmer Issues: https://forums.eagle.ru/topic/221282-bugs-fc3-autopilot-trimmer-control-issues Fresh install, toggled Fullscreen, VSync, turned off all new UIs, disabled Mouse Acceleration in Windows, updated Video drivers, disabled Windows Fullscreen Optimizations, modified CockpitMouseSpeedNormal, Fast, Slow in View.lua, checked FPS counter to rule out performance issue, etc... Seems similar to the following problems, and some other random reported TrackIR issues: 'Sticky Camera' and 'Speed Gates': https://forums.eagle.ru/topic/252576-already-reportedsticky-external-camera-movement-with-high-polling-rate-of-mice/?tab=comments#comment-4510696 View stutters due to Mouse Polling Rate: https://forums.eagle.ru/topic/228705-view-stutters-when-i-move-my-mouse-around/?tab=comments#comment-4211585 It's not just a 'speed gate', although that effect is noticeable. Something related to aircraft panels and objects is affecting the speed as well. Polling rate 'fix' is a temporary workaround: 100mhz polling +10ms input lag, 125mhz polling +8ms input lag. It also does not remove the effect completely, only reduces it, while increasing sensitivity. If you reduce sensitivity in View.lua to match, the effect becomes noticeable again, and the 'lag' is unbearable anyways, due to large 'jumps' in view angle. Better workaround: Set Axis Tune Curvature to ~20 for Mouse X and Mouse Y Axes. It's not a complete fix, but it's better than polling rate hack. Just a reminder: 2014, bruh... "In new beta update manual trim and t/o trim may not work. It's known issue. Please, do not make new topics" 2021, bruh... Still in beta...

If possible: Probably not worth the effort, but if it's simple enough, Combine Flaming Cliffs 3 aircraft and Su-25T Gear Light Far/Off and Navigation Lights On/Off into a single keybind. The state of one when other is toggled doesn't matter from a functional perspective, but eliminates the need to keep track of external lighting state by the pilot and by scripts. Convert HUD Brightness Up and HUD Brightness Down into a single toggle switch that cycles between High and Low Brightness. Or add another keybind, similar to Flaps Up/Down.

Circular analog input devices aren't translated correctly in Windows. It isn't possible to achieve 100% yaw/pitch/roll on the diagonal in the default configuration (calibration), only 70.7%. Affects all circular analog controllers, unless somehow supported by driver or software natively. The only workaround is to recalibrate the device, but that reduces the range of motion available to the controller, effectively making 29.3% of the range worthless if you want 100% yaw/pitch/roll on the diagonal. VJoy, Autohotkey, etc... cannot solve this issue. Actually possible with x360ce (assuming it works in DCS), but only by editing the source code and compiling (questionable example): https://www.ngemu.com/threads/circle-to-square-analog-mapping.155968/ Maybe also Joystick Gremlin, but not sure, and I don't do Python scripting: https://whitemagic.github.io/JoystickGremlin/user_plugins_code/ The only real in-game solution would be something like this (may introduce input lag and require pre-calculated tables instead): http://theinstructionlimit.com/squaring-the-thumbsticks I thought there was an option to fix this issue in-game, but apparently not. Not sure in which game/application I saw an option like this previously. Calibration can be done programmatically through Control Panel, or by setting Axis Saturation X (not Y) values in DCS configuration. HKCU\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_045E&PID_028E\Calibration\0\Type\Axes Axis 0 (x): 00 0f 00 00 00 80 00 00 00 f0 00 00 Axis 1 (y): 00 0f 00 00 00 80 00 00 00 f0 00 00 Axis 2 (z): 80 0f 00 00 80 80 00 00 80 f0 00 00 Axis 3 (rx): ff 0f 00 00 ff 80 00 00 ff f0 00 00 Axis 4 (ry): ff 0f 00 00 ff 80 00 00 ff f0 00 00 Axis identifier: 00 (x/y), 80 (z), ff (rx/ry) Axis range: 0f (15 min), 80 (128 center), f0 (240 max) Unknown: 00 00 Will set the saturation (of controller input motion range) to 87.5% for example (or set Axis Saturation X to 87.5% in DCS config). 16/128 (half range, full 0-255) = 12.5%. To reset calibration, delete the reg_binary values or use control panel to reset joystick calibration (same effect). To populate reg values, calibrate it.

Not related to the F/A-18, but Autopilot is questionable in some FC3 aircraft, so it may just be busted. See [bugs] FC3: Autopilot + Trimmer control issues: https://forums.eagle.ru/showthread.php?p=4149441 As mentioned already, set a Deadzone. Gamepads require 5-10 due to loose sticks, maybe less for more stable sticks. Some aircraft will disengage autopilot after 5-15 degrees of pitch/yaw, others won't. Setting a curvature also helps to prevent tripping the threshold of 5 degrees. In terms of modes, I can only tell you what works in FC3: A-10A engage by hitting correct mode button and Engage/Disengage. Disengage with Engage/Disengage. For other aircraft, just hit the correct mode button directly, ignore Autopilot (engage) hotkey. Disengage with Reset Autopilot.

Edit Axis Commands for JOY_X/Y/Z/RX/RZ and select Axis Tune button near the bottom. Set Deadzone to 10 and Curvature to 50. You can adjust them as needed, amazing for gamepads, which have an even smaller range of input and loose analog sticks. You really have to flatten that curvature for the first few degrees of input.

Trim Rudder: F-15C: Trim Rudder Left/Right trims Ailerons instead. No characteristic yaw effect, as opposed to all other aircraft. Rate of trim is also sluggish vs other aircraft. Trim Reset: A-10A: Does not reset Rudders. F-15C: Lacks Trim Reset. Does not reset Rudders, since Trim Rudder Left/Right don't work. T/O (take/off?) Trim trims nose up, no difference, also bugged. Su-25: Lacks Trim Reset. Su-25T: Lacks Trim Reset, but Autopilot can be used as a pseudo-Reset. Su-27/33, MiG-29A/S/C/G, J-11A: Trim Reset works and also resets Rudders. Autopilot: F-15C: Autopilot doesn't work. MiG-29A/S/C/G: Barometric Altitude Hold doesn't work, but the 'H' version does. Both function in other aircraft. Su-25: Lacks Autopilot. A-10A, Su-27/33, J-11A: All tested Autopilot features work as expected. Autopilot Trimmers: Su-25T: Autopilot sets trimmers, but lacks Trim Reset. MiG-29A/S/C/G: Autopilot sets trimmers, but they can be reset. Autopilot Reset: MiG-29A/S/C/G: Lacks Autopilot Reset. Autopilot Reset (Stick Button) must be held down for 50ms (via script), but standard (non-Stick Button) version doesn't have this limitation, otherwise functions identically. Summary: Su-27/33 and J-11A, based on the same design, function as expected. F-15C is completely broken. A-10A, Su-25/25T and MiG-29A/S/C/G are in various states of disrepair. Resolution: A-10A: Trim Reset should reset Rudders. Su-25/25T: Add a Trim Reset hotkey. F-15C: Fix/Add Autopilot, Rudder Trim and Trim Reset functions. MiG-29A/S/C/G: Add an Autopilot Reset hotkey and fix Barometric Altitude Hold. Su-27/33 and J-11A: In working condition. Notes: Barometric Altitude Hold 'H' maintains Heading when banked less than 6/7 degrees, otherwise maintains Roll. No different from non-H and Roll Hold versions in Su-27/33. Tested: Autopilot Engage/Disengage and Disengage, Autopilot Reset and (Stick Button) version, Barometric Altitude Hold and 'H' + Roll Hold versions. I can test other options and radars/weapons if needed, but at least let me know you'll fix these first, before I buy F/A-18C. Thanks.:helpsmilie:

Save a SnapView using in-game commands, then edit SnapViews.lua and copy the snapview angles you just saved to the 'default view'. Whenever you push the 'View Center' keybind, it should recenter the screen to the default view.

You can edit the default position in a file called SnapViews.Lua (per aircraft, file contains views for all). You can also save snap views from within the game, the get the correct position. However, you may have to copy the snapview angles inside the file to the 'default' snapview, as I'm not sure which view (default or 0-9) affects VR and TrackIR. Some of the views are designed to zoom in on instruments or left/right panels, others are general directions, and one is the default which is used for the key 'center view'.

Delete this post, updated here: https://forums.eagle.ru/showthread.php?p=4149441

I ran into a few problems with the previous config, then just dropped it for some time, since there wasn't much interest. I recently fixed all of the issues associated with it though and am just fixing the last bugs. I'll post the completed version in a few days, or maybe in the New Year, as schedule gets a bit crazy.:pilotfly: Had to swap trimmers from DPAD, since using a modifier to swap between trimmers and target designator was cumbersome, which required a complete reconfiguration of assigned buttons. Trimmers on DPAD also make landing cumbersome, since you have to release the left analog control stick to adjust the trimmer. Most of the other controls were modified to fit the same scheme, where Shift Mode (LB) now primarily swaps between combat and navigation modes. Chute + Hook were conflicting with airbrake and Shift Mode. Still contemplating making Unlock Target and Throttle Down (hold) keys instead of Shift Mode. Added support for J-11A and MiG-29 variants. No plans to add TF-51D Mustang at this time. Controls are completely different, maybe when I manage to simplify A-10C.

Note: This is a preliminary post to gather some feedback. I will update this post with the required files in a few days, when completed. See 3rd post for updated image. This configuration allows you to fly any Default and Flaming Cliffs 3 aircraft using only an XBOX 360 Controller, with optional Mouse, VR or Track IR to control the view. Gray keys represent 'shifted' commands, active while holding the controller's Left Button (above the Left Trigger). Requirements: Mouse: A middle button (to center view) is required. Mouse Wheel is required to control zoom level. VR / Track IR: A mouse is not required to control the view. Keyboard: Only required for taxiing, carriers, refueling, rearming and lighting. Functional Aircraft: A-10A, F-15C, Su-25/25T, Su-27, Su-33, MiG-29A/S/C/G, J-11A Autohotkey: Custom .ahk script is required to allow a wider range of controller axis and mouse binding assignments, unify several keys/functions, and fix some controller issues.

ColorAliesSide = {249, 69,38} ColorEnemiesSide = {0, 72, 199} ColorUnknown = {50, 50, 50} -- will be blend at distance with coalition color Appears backwards in Labels.lua, but allies are Blue and enemies are Red in Flaming Cliffs 3 Instant Action missions. Haven't tested anything else. 'Alies'. Blur color also appears backwards. Actually, RU are red, US are blue, and the rest of the countries fall somewhere between. Now that explains RU being 'Alies'. US is enemies. Enemy is blue! ;p

Generally, anything higher order in the Z-buffer (depth buffer) is not rendered. Known as Z-culling. This applies to nearly all games post-1995.