SloppyDog

Yes, it does, and it is very noticeable. While the pedals are coupled with the cyclic, we will experience this problem. I found that the best way to fly the Chinook in the current state is to use the Force Release as little as possible, and controlling helo as a airplane, using the newly available trim hat. No problem here. Maybe you have set the controls thinking of trim, inputting the UP position of the trim hat in game to a down position on your joystick. In order for it to work right you must set up to a up button and down to a down button. Also, I could not set the CD REL to a button of my own choosing. The only button the game accepted was the Default option. In my case, it set the CD REL to button 03, which is a badly positioned button that I rarely use.

I've been experiencing something similar. Once ATT and ALT hold are engaged, the aircraft starts to accelerate or decelerate, and the ALT HOLD can not maintain altitude. I'm able to counter the accelerating or decelerating tendencies by re-trimming the aircraft to a position where the speed is maintained constant. No problem there, since it is Attitude hold, after all. Just a slight re-trim, that's it. However, even in a constant speed state, the altitude starts to drift slowly, to the point I get a SAS Saturated message and later on a Altitude Drift Warning. I have to retrim, and engage ALT HOLD again. Another point I noticed is that the SAS Saturated message shows up with the controls at half of their total deflection. At least it is what is shown on the second controls indicator. Before, the SAS Saturated would occur only when any of the axis were at its corresponding stop.

This single phrase defines helicopter aerodynamics perfectly. Can you provide a track? I would like to see the kind of maneuvers you are doing. Anyway, as ED stated, the SCAS is a WIP. Maybe for some cases it is happening, maybe not. And we must have in mind that DCS physics are not perfect and a lot of times it does not follow expected real life behavior.

Too much turkey... I could think of one or two jokes about it... Too much turkey and a helo, you'd get AirWolf. Anyway, RBS is Retreating Blade Stall. When a helicopter starts to moving too fast, one side of the rotor disk will have more lift than the other. In the case of American helos where the rotor turns counterclowise, the right side of the rotor will have much more lift than the left side. This goes up to the point that the left side stalls and loses lift. As the helicopter has a lot of lift on the right side, and no lift on the left side, the tendency then is to helicopter to roll to the left. But here is the catch: due to the gyroscopic effect, any command, controlled or not, in any part of the disk, will manifest itself with a delay of 90º. As the lift increases on the right side, the effect is felt 90º later , meaning it will add lift to the front of the rotor disk. This excess lift at the front will make the helicopter pitch up. Combined with the loss of lift on the left side, the helicopter will pitch up and roll left. What I believe others are experience is that in a dive, the Apache is exceeding the Never Exceed Speed (Vne) for that situation (heavy, with fuel and weapons load).Thus, when diving, the speeds increases and the retreating blade stall reaches its limit, the helicopter rolls left. Maybe the effect is very pronounced in the DCS Apache, I will have to test it later. Here are some videos that help understand dissimmetry of lift and retreating blade stall:

In the December 24th, 2024 update, they said they fixed it: DCS 2.9.11.4686 DCS: P-47D Thunderbolt by Eagle Dynamics Fixed. Engine degraded with WEP usage I have to test it though.

Here are somethings I've noticed after a long test flight: Low speed handling is much better. No more tail whipping like crazy when inputting collective. As you slowly input collective, it will cause the normal torque reactions you would expect from a helicopter, but not crazy oscillations as before; Other collective/tail rotor related thing I noticed is that at high speeds, I could change altitude by "slowly" inputting collective without the tail whipping around or crazy oscillations. In more than one occasion I could input collective hands free of the cyclic. Att Hold: sometimes it tends to accelerate or decelerate, but I learned that I need do counter it by trimming at the desired speed and leaving it there. Alt Hold, on the other hand, is not holding that much. I get a SAS saturated warning, the altitude starts changing, and then right after I get a Altitude Drift warning. Maybe it is my controls, looking at the cockpit cyclic is is trembling up and down. I know my controls are old and use potentiometers, maybe this is causing this oscillations. Crabbing: it does crabs, but not a lot like before. It tends to compensate for the wind where there is wind, but where there is no cross wind, it seems to be flying much more straight now. Position HOLD: seems to be working fine, tested it with some crosswind and stayed in position. Further tests are needed. From the changelog: Helicopter SCAS - known issues When turning ON or OFF the Position-Hold mode, several damped oscillations in roll and/or pitch may occur The oscillations do occur. It is annoying at first. What I learned to avoid them is to keep the cyclic at the position I want and not move it. Let the oscillations resolve themselves. Although, the helicopter tends to pitch up. I have to input a lot of forward cyclic to counter it, when accelerating from zero speed. Maybe it is related to my curves setting on the controls. I'm using 100% saturation and a 25 curvature. Will test later without the curvature. Ground taxiing: much better. Just push the cyclic forward a bit, set the collective to 30% and here you go. When unlocking the tail wheel, it still tends to snake around, doing S-turns, but it is much less noticeable now. Curves: cyclic curves on my controls were at 60% saturation, on the X and Y axis. Since the controls sensitivity where reduced, I cloud, actually, I needed to get them back to 100 % saturation. It shows how much the response to pilot input has been improved. Overall, a much better experience, no more crazy reactions when inputting a small amount of control, be it cyclic, collective and pedals. All in all, if you behave when inputting controls, the aircraft will behave as well. This didn't happen before. Attached is the track from the long flight test. Apache Flight Test- Post December 24th Patch.trk

They've taken out a lot of sensitivity from the pedals/tail rotor. It is much more flyable now. Regarding the pitch up attitude, I've noticed it when you are taking off or from hover to speed up. It has a pitch up tendency, that I need to input a lot of forward stick to compensate for. And about the trim, I did not experience what you have been experiencing.

Don't know about the drift, have to test it. Regarding the pitch oscillations, they noted it on the changelog: Helicopter SCAS - known issues When turning ON or OFF the Position-Hold mode, several damped oscillations in roll and/or pitch may occur

Thank you for the update! Merry Christmas!

I could not make the old DCS Bios detect my DCS Open Beta installation. Also, I tried using Bort console to use the function to get the indications, but it presented erros. Does anyone know how to use a Lua console with the new DCS Skunkworks DCS Bios?

Cool! Good to know. I like it a lot, just because it looks way cooler!

No problem, man. Thanks for the compliment. As a teacher in real life and a curious by nature, it was a good challenge to learn all this. I'm glad you liked the way I explained it. It was very useful for me as well, because I'm trying to do the very same thing, but for the F-15E.

Ok, if you are trying to set a trigger based on a radio frequency set in the Remote Frequency Indicator, I think I have this figured out. It was an interesting challenge to learn how to do it. In order to detect a parameter from an indicator in the cockpit you need to use the function X: COCKPIT INDICATION TEXT IS EQUAL TO. This function asks for three parameters to be filled in order to work correctly: INDICATOR ID ELEM NAME VALUE ---------- INDICATOR ID Indicators are anything that present a value to the crew. In the case of the Remote Frequency Indicator (RFD), or any indicator, you have to find its ID. The ID for indicators are normally inside the Cockpit folder for the module, referenced in the device_init.lua file. For the Kiowa, this file can be found in the \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit folder. Inside the device_init.lua you have to look for the indicators section. I am using the Notepad++ software to open the lua files, and I recommend that you use it too, as it identifies the line numbers. I'll be referencing the line numbers from now on. The indicators section starts at line 82. The RFD is listed on line 91. From the DCS User Manual, page 166, it is stated that the indicators ID start at 0 and increase by 1 with each subsequent line. So, if you count from line 83, "OH58D::ccControls Indicator", considering it as 0, to line 91, "OH58D::ccRFD Indicator", you will end up with 8. This is the INDICATOR ID you are looking for. ----------- ELEM NAME This is the tricky part. You have to look for the Main_page.lua file inside the indicator folder. For the RFD it is inside the Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit\RFD\Indicator. As you are looking for a frequency showed in the RFD, you have to look for the Frequency section inside the file. Using Notepad++ it is on page 134. The ELEM NAME is always listed as "Something.name". In the case of a radio frequency, on line 140 we found Freq.name. Freq.name = "Freq".. string.format("%i", i) So, we have the first part of the ELEM NAME, Freq. The Freq is inside a for loop, counting from 1 to 5, as shown on line 136: for i = 1, 5 do So, as we are interested on Frequency 5 on the RFD, the string.format("%i", i) will be 5. Thus, the ELEM NAME is Freq5 ----------- VALUE This is the easy part. It is a simple string. Sometimes it requires the dot,sometimes it doesnt. In the case of the A-10C it was not necessary to input the dot; in the case of the Kiowa it was needed. Pure trial and error to find out. I chose 055.000 Mhz as the desired frequency to activate the trigger, thus the VALUE in this case will be 055.000. -------------------- Now, you can get in the Triggers section of the Mission Editor and input the parameters For the Triggers I created a Switched Condition, so that every time you input the right frequency the trigger will be activated. The Condition is the X: COCKPIT INDICATION TEXT IS EQUAL TO, with the following parameters INDICATOR ID = 8 ELEM NAME = Freq5 VALUE = 055.000 The Action is a Message to All ----------------------------------- I made a mission using two A-10C as testbeds and a Kiowa. For the A-10s, every time you input: Preset Channel in the UHF radio equal to 02 or; A frequency of 255.000 Mhz in the UHF radio, a message will appear. For the Kiowa, every time you input 055.000 in the Radio 05, a message will appear. Attached is a track file showing the operation in the Kiowa and the mission I used for the tests. Oh-58D Kiowa RFD Frequency Trigger.trk A-10C-Radio Text Test.miz

If I'm understanding it right, you want to set a trigger once a certain frequency is set on the Radio Frequency Display. There is a Condition for it in the mission editor called X: COCKPIT INDICATION TEXT IS EQUAL TO. However, as stated on the page 166 of the manual, this particular function 'requires console'. Said 'console' is only available to developers, so they can trigger cockpit or model arguments based on text displayed on the various display of an aircraft. But it does not stop you from trying. Following the instructions laid out in the manual, in the \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit folder there is a file called device_init.lua. By the manual instructions, the RFD on line 91 should be indicator ID '8'. So, by using this condition, maybe you will be able to trigger the condition you want. The hard part is to find the string correspondent to the R5 frequency. Maybe DCS-BIOS can help you with that.

The Flight Directors work great for the most part, and it is a great addition to the sim. I just imagine the amount of work was necessary to create something like this. In the SuperCarrier manual we have only a small glimpse of the path logic for the aircraft and the yellow vests. However, I would like to report some things: 1) At the current patch status, the Flight Directors ignore parked aircraft, static or AI controlled, being blind to them. The FDs send the player to the catapult or parking spots with other aircraft in the way. Attached is the track for the default Cold Start mission in the Kola Peninsula, for the F/A-18C. Flight Directors send the player to a catapult filled with parked aircraft. I've tested in other mission the parking logic after landing, and the same happens, the FDs sent me to a spot already occupied by another aircraft. Other issues noted: 2) The option "Enable Velocity Limit while taxi" in the Special Tab is not working. Even when you uncheck it, the speed limit is enforced. 3) Could not see any difference between "Enable simplified taxi signals while taxiing to catapult or parking" on and off. A video of the Kola Cold and Start mission is available here: F-18-Kola-SC-Cold Start- Blind FDs.trk

Look for the radio ID in the arg_int.lua file inside your "DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit" folder. I believe it is the RMFD_R5_Button = 82 argument. On how to use it, you can refer to the Cockpit Triggers Guide on the DCS Manual. It shows how you use them, the arguments you have to add to make it work.

Yep, same thing here. I loaded a CFT with 4 x GBU-12s and the option for fuzing does not show up. The same goes for the bombs laser code.

I looked in the module manuals and in Chuck's Guides and the only warning regarding the weight is that it must not be above 20,500 lbs. No notes regarding the conditions at this limit is applicable. But, it may be for ideal conditions. For higher altitudes and temperatures this limit must be lower. The maximum values for Fuel and Water (F+W) should be given by the VREST VL page for the atmospheric conditions at the moment of landing , but I tested and it seems that they are not working properly.

Good improvements to the core game. The white paper on the fog shows how difficult and complicated things can be to implement. but the end result should be very satisfactory. Also, SuperCarrier Marshalls! Finally!

It is way better to fly now. I had given up on this module, but yesterday I was trying it and had a blast flying! @Spankinvicar in the Instrument Power Train Format Page (page 66 in the manual) you can see the LFC actuators moving position forward or aft (they move independently) as you go faster or slower. They start moving from 60 knots to 150 knots.

Thanks. Very cool indeed. I've teste the AAA mission and the light show is amazing.

Thanks for sharing. This is exactly what I've been looking for some time now. I want to make an automated WSO for the F-15E. The idea being simple tasks like setting his cockpit up after mission start, turning on the TPOD, setting up PACS including programming the weapons page.. up to more complex tasks like doing Fence In and Fence out tasks. Also, in order to make him more human like, I was looking for this delay between actions, like he is thinking about what to input and reading off of a mission briefing. This will be VERY helpful, I'll test it and come to you back later.

A realistic inertial alignment in DCS? Count me in!

"These waypoint types include Identification Point (IP), Target (TGT), Visual Identification Point/ Nav Fix (VIP), CAP station between two subsequent CAP points and according QnA to set the desired vul-time (CAP), FENCE-IN (F-IN), FENCE-OUT (F-OUT), Homebase (HB), and Alternate (ALT), allowing for more sophisticated mission planning and execution." And in the manual it is stated: "Fence In (F-IN) and Fence Out (F-OUT): These waypoints function similarly to the IP and Target types, but with additional tasks." Also a warning (or note): " For Fence In and Fence Out, Jester will later also guide the pilot through specific checklists." So, are we going to see something similar to the Wizzo on the old and venerable Jane's F-15? In that game, the WSO was a great part on making the game feel alive. Also, when you hit the target he would celebrate, with some very funny phrases. I saw in the mini-campaign trailer that Jester says something like that when the target is hit. P.S: I started to making decent landings and Jester does not say something in the line of "my mustache is fusioned with my eybrowns" anymore. Should I get worried? Or celebrate?

Here you go. the mission files is attached. Mega Range - No Ultd Ammo.miz