skypickle

@Trigatithank you for this work. @AhSoulnice profiles. I am working on a 'checklist oriented' profile. For example inside a folder labeled, 'start', is a sequence of buttons and switches from left to right that represent the actions needed to start the aircraft. Following the buttons in order is like reading the checklist. Although not a realistic representation of the actual button arrangement in the aircraft, it prompts me to remember the steps in order. I can post it if you find this an interesting approach but there are no pretty icons. But when it comes to weapons employment sequences ,this leads to a lot of duplication.

the discord invite is invalid. new one?

Figured out my issue. Desktop capture was not enabled in Geforce experience privacy settings. Turned that on and now it works.

I can take screenshots with it but the vodeo functions seem off. When i hit the hotkey to record, it flashes a notice that it started recording but immediately flashes a notice that it stopped. And no recording is saved. Also, the hotkey for saving the last 5 mintues does not work. I tried changing the hotkeys, reinstalling the drivers but no joy. Win 10 pro,latest dcs open beta.

still happening. Event log says: Faulting application name: dcs_interface.exe, version: 0.0.0.0, time stamp: 0x60e65799 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x3128 Faulting application start time: 0x01d9ac1ca80e4038 Faulting application path: C:\Users\Stefan\AppData\Roaming\Elgato\StreamDeck\Plugins\com.ctytler.dcs.sdPlugin\dcs_interface.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 792901a3-34cc-4898-b53e-48a3d637cada Faulting package full name: Faulting package-relative application ID: I get 10 of these errors in succession each with a different process id. Looks like the plug in crashes and restarts. Restarting streamdeck doesnt fix it. Need to restart the game from scratch

@AhSoulI noticed in the streamdeck profile you posted in the user files, the font has been increased to 11 from 9 and the button icon is a little different. Were there any other changes?

I figured it out. Unchecking a special option (module individual force feedback toggle) restored full excursion of the indicator. The chopper is also easier to control now. What is this option supposed to do? Even unchecked, my force feedback stick still provides force feedback

I have set saturation to 100 and no curves for both pitch and roll. My controls indicator shows the 'diamond' moving less than half way away from the center with full stick excursion.Your image does not show the controls indicator. I did notice however that polychop has added 'builtin' curves. look at how much the control moves in the on screen indicator. near the zero point, moving the stick causes comparatively little motion. as you move away from the zero point the the indicators move more for the same amount of additional stick excursion.

1) no reticle on pilot sight when using mistral. And even though I have a target in front of me, I never get a lock tone 2)excursion of the controls seems limited. see the attached pic. When trimmed for level flight, I have the cyclic pushed all the way forward and to the left yet the control diamond on the graph (in the upper left of the pic) shows it only halfway there. Is this intended?

thank you for working this out but where do i put these? in monitor config.lua i am using?

I think some of the instability comes from ‘human desync’ issues. If you look at the engine behavior during startup you’ll see that there is a lag between your collective inputs and engine response. There is also often some overshoot. When you start to pull pitch, if it’s done too quickly, youll hear engine warnings. After I noticed this, i changed my collective inputs to small stepwise changes while watching the engine page-waiting for changes to stabilize after every input. This has allowed me to actually do a proper hover check without much tipping or wandering

The three counterclockwise choices put the camera in travel, standby and off modes. The clockwise choice locks the camera to the previous targets. So yes , that is the selection that allows free camera movement

yes i can but you have to be in 'pilot mode' null

yes you can

even look at the you tube video posted above which has the english cockpit. you can clearly see the word 'night' below the bottom right unlit green led.

The button to switch from IR to TV works in the cockpit. However, if that function is bound to a button on a joystick or a keyboard key, then the button is depressed but never pops up, evern if repeatedly pressed. You have to move the mouse in the cockpit and click the button to get it to release. However, the keybind seems to work in actually switching TV and IR.

thank you for making this video on cranking. but where is it on your website, https://flyandwire.com/ ?

There are bindings for the landing light to be on,off, or vario. However, i do no find an axis or other control for raising or dimming the brightness of the landing lights when they are on vario.

what is it called because i am not seeing it.

Thank for these videos. Very helpful. But why did you change the titles to OUTDATED? What is outdated?

If the minigun is activated and mouse control enabled with alt-C, it works fine in game. But if you move the mouse to a second screen (maybe to watch a youtube tutorial) and click, the minigun starts firing. The only way to stop it is to move the cursor back into the game and click again. Mouse inputs on other screens should be ignored.

Thank you. I didnt realize there was a 'decouple minigun' until you posted this. Using the mouse is much easier than TrackIR to aim.

OK. I got this to work with the mouse but first I have to press L alt - C (clickable mouse cockpit mode ON/OFF). I also had to check 'decoouple minigun' in the special options.

yes, i waited a long time even after it was announced completed.

@Raptor9i find a significant difference in dcs between force trim release in the huey and the apache. Because the scas actively alters control inputs, when ftr is depressed in the apache the sudden absence of those inputs can lead to wild changes in attitude. This is not force trim release overshoot due to the pilot’s hand accidentally moving after resistance is released because my hand does not move when i depress ftr. The force feedback stick i use provides a clear and significant resistive force but it is not a lot. I can continue to fly the bird w fingertip control at all times. However ed may have modeled and simulated this behavior so when ftr is depressed this wild behavior happens even though there is no stick movement.