Yeti42

I honestly think there is no harm in making an easy option for inflight refueling, as long as mission editors are able to enforce the option not to on servers. I doubt any major servers would allow it anyway. I struggled with it to start with and eventually confronted my daemons, it took about 2 weeks and 5 hours practice to get there, not unreasonable I thought. For me, making it easy rather defeats the point, but I can understand people not wanting to deal with it on a mission.

Just because the lines are commented out doesn't mean someone is working on it... what it means is someone realized it was incomplete "at some time" and wanted to put a placeholder in. Those comments could have been there for a while... we really have no idea if it's being worked on just saying.

RAG was never intended for non emergency landings. For off field landings on roads etc. it was also deemed impractical as this increased the equipment needed and the footprint. I worked on Jaguar GR1's and Tornado's during the cold war and was involved in various trials involving off field distributed operations, none of the off field sites were equipped with arrester gear, this also goes for any other aircraft I was aware of. It would be great to have this feature for runways, especially given the advances that are coming with system modelling on the F4 and similar aircraft. Hydraulic failures were one of the major causes for mishaps when I was an engineer, these type of failures invariably involved the use of the RAG system and were fairly common.

The two threads are different behaviors, they may have the same root cause though. I have to say looking at the new flight model the improvements outweigh any issues, it still needs fixing, because us a**l people will always find something. It's not an easy task developing a fly-by-wire model, that's why it takes years and costs millions in the real world

See this:: Two threads have been merged both relating to FCS behavior, my thread was complaining about uncommanded nose up behavior after a touch-and-go

TO trim button was the first thing I thought of, It didn't work, I still had reduced pitch authority when I encountered the first issue, bearing in mind this was after the onset of the issue in flight with the flaps at half. My suspicion here is that the FCS somehow gets stuck in landing or approach mode and the FCS has an argument with itself when you command pitch down , I've no idea if these FBW modes are modeled in DCS.

OK, I've managed to reproduce similar behavior as the original issue but not exactly the same. You'll see in the track file I'm doing lots of approaches with different parameters and some missed approaches, the last one in the track file is a touch and go which demonstrates the behavior. I don't select gear up and give mill power without touching the stick. As expected I pitch high but I'm unable to recover even with full stick down and trim, selecting gear up seems to re-instate full pitch authority. EDIT: attached the tacview file from the original occurrence, this is all I have from the first time it happened but it demonstrates the issue well, note I was applying full nose down at the end when the roller-coaster was occurring F18_AOA.miz.trk Tacview-20240223-120901-DCS-IA-FA18C-Syria-Free Flight.zip.acmi

Yep, I'll work on reproducing it and remembering to save the track file

I'm not raising a bug yet, I just want to know if anyone else is experiencing unexpected behavior: My first flight using the new flight model was an instant action flight on the Syria map, I flew around for 10 minutes or so testing the AOA capabilities and then decided to dump all stores and do some touch-and-go's at Incirlik. To cut a long story short, the landing was fine as was on AOA during finals and touchdown, the problems started when I selected 1/2 flap, military power and rotated after touchdown. The jet adopted an increasingly nose-high attitude which I was unable to counter with full forward stick and manual nose-down trim. The result was inevitable and the jet departed. Has anyone else seen behavior similar to this? I've been unable to reproduce the behavior in the 2 short flights since and the track file has been overwritten.

So regarding the Deployment Campaign conversion to BS3.. I'm working on the final mission (Mission 12), unfortunately this will require an almost complete re-write! The problem is the mission is based around intercepting a convoy and attacking a rebel base, the newer Caucasus map is now populated by a lot more trees and the convoy route is now completely off-road, coupled with the new weather and enhanced rain effects you can't see s***t and even if you could the enemy is completely obscured by trees! Remove scenery trigger doesn't appear to work for large areas anymore so I need to re-think the whole mission's location and alter the associated triggers. At LEAST a weeks work sorry for the delay

I've nearly finished converting the "Deployment" campaign to BS3. I think it's one of the oldest campaigns so there was quite a lot of work involved and I had to fly through every mission multiple times to fix them. Apart from simply changing the model to BS3 in the ME, I also checked the weapons load-outs, the correct helmet-mounted device (defaulted to NVG normally) Set INU to no alignment needed, removed trees from areas with targets where there were no trees originally, changed some AI load-outs for SEAD where the AI was useless, plus a few more tweaks which make the missions slightly more achievable. I also cut some of the longer mission routes which involved flying for ages and then not having enough fuel. Will upload in hopefully a few days from now. Edit: Finished! Attached zip file, search for user pyates2104 Deployment Campaign for Black Shark 3 (digitalcombatsimulator.com) BS3_Deployment.zip

I'm guessing you mean in-game and not in the mission editor... So the quick answer to this is no not really. The weather and date/time is stored in the mission *.miz file so the only way would be to unpack the mission file after start, edit the values in the lua somehow, save it and then reload the mission, defeats the point somewhat and is ugly.....

I would use the HaptiConnect software from Buttkicker which now works with DCS. The recommended way to use this software is NOT to use the headset splitter and connect the amp directly to your Buttkicker. Normal in-game sounds should then continue to your speakers/headset as normal, the telemetry from DCS aircraft drives the Buttkicker not the sound coming from the game.

Having worked on INS equipped aircraft with no GPS in the past, I can confirm that ground crew would typically align the INS and switch to Nav before the aircrew arrived.

This is a solution to a problem I was having with my Winwing MFCD's but it applies to all multi-display setups, thought it may be useful for anyone else having similar problems: The issue was Windows sometimes displayed the main game window or other app windows on one of my small usb displays which I use in DCS for MFCD's. The was a pain as it was difficult to get the window out of the display without unplugging it. 1. Microsoft has a small console utility called "PnPUtil" It's already installed on windows (10 and 11). The utility basically allows you to select devices and enable and disable them on the console by using the device id or instance id, the same as you would using the device manager UI, and a whole lot more. 2. Simply create a batch file to enable and disable the unwanted displays when you are not using DCS. You can then either create another batch file to enable them or just use that in a custom DCS start bat, simples, solves all my problems. Note that the batch file needs to run as admin or it won't work, simply create a shortcut for it and select run as admin in the properties. You can also use a similar script for disabling any device for driver updates, particularly useful for WinWing device updates. Full info on the util syntax can be found here PnPUtil Examples - Windows drivers | Microsoft Learn Example, you need to enter the ID of your display as found in the device manager obviously: Disables displays Echo yadyayada pnputil /disable-device "USB\VID_045E&PID_00DB\6&870CE29&0&1" pnputil /disable-device "USB\VID_045E&PID_00DB\6&870CE29&0&2" pnputil /disable-device "USB\VID_045E&PID_00DB\6&870CE29&0&3" Exit Enables displays Echo yadyayada pnputil /enable-device "USB\VID_045E&PID_00DB\6&870CE29&0&1" pnputil /enable-device "USB\VID_045E&PID_00DB\6&870CE29&0&2" pnputil /enable-device "USB\VID_045E&PID_00DB\6&870CE29&0&3" Exit