McNasty_UK

I'm having mixed results with Flight Comms. (Who isn't ;¬) Yes I've seen the video. In the end I mapped a button for Comms and one for Radio. One always seems to work. Somewhere about mission 6 I got talk back but all gone quiet again. Could you confirm which channel we need for wingman/flight please I. II, Triangle or Square. Mission 10 I found out you can tell the flight to Attack, Form up or RTB using the F10 and they reply. Only three option commands though. The other F# options Navigate, Wingman, formation etc no reply. From day 1 I've been using the German speech commands mod. It's brilliant ! It really adds to the scenario. I am wondering if this has kinked my coms replying though? Keep up the excellent Campaigns ( I have Debden Eagles also). I would recommend buying Reflected campaigns rather than slogging it out trying to write and tinker your own for the price.

This is what I settled on using just USB and Hapti connect. See pic. USB to BK amp for Hapti USB external sound card audio output to BK using straight audio connection. For SSA &SSM Using Sim Shaker for Aviators with the Sim Shaker Module I got mixed results. You can download both for free and SSM has two free files (Road rumble and 1 other.)for testing purposes. I was able to get BK to run using SSA & SSM (click the test buttons) but as soon as I switched it to DCS...nothing.. Weird. Andre did answer my post but it's still not working correctly. Added to this the Sim Shaker Sound Module you pay for the full suite ( if the two free files work). Being based in the Russian Federation all pay options are frozen out currently. I was offered an alternative route to pay with but I wasn't too keen on that as I didn't have" that type " of credit card. So BK & Hapti works most of the sound options. Overall I'm happy with it. Flying without it is when you do miss the bumps & clunks. I just wish Hapti would improve their software.

24hrs now since I installed BK Plus & Haptic . The instruction manual doesn't come with a wiring diagram. May sound stupid but a bit of explanation via a diagram would of helped. I couldn't get BK to run on USB input without taking its signal from the PC audio port (wired up with the Y cable as instructions) Despite it says if you have Haptic open then audio will not work. But it did I didn't see the point of the audio cable if you've got DCS &USB. The telemetry is supposed to be better then SSA etc. I unplugged the audio and went USB only. It was then I discovered configuration of the input/output devices were incorrect. Again the setup manual was lacking explanation/ pics. I concur with the above.Chaff doesn't seem to work or Wing fold. However Speed brake does. Taxi surface seems borked too. I get the odd thud (which could be suspension or brakes) but no road rumble so to speak. The software sliders are quite sensitive so be prepared to do a bit of testing to get your desired levels. For my rig I went with the BK Plus. I mounted it via the three screw holes to my flight seat at hip level Lh side. For those guessing Plus or Pro, I'd say the Plus is good enough unless you have a full size monster rig. Currently I'm configuring the F/A 18. Next will be the P-51D. I guess another day of testing. Advise and tip appreciated.

I think the tool for the job would be an A10 Warthog. Target rich environment ! Imagine how the ground forces would of been grateful for a squadron of those and a JTAC.

Smashy, BOOM! Your LUA file mod works a treat. My Gunners are back..GET SOME ! All, You have to use Notepad ++ ( Free download off the net) and backup the file.Call it OriginalUH1.Lua or something. THIS file is in your DCS root install. Not c:\savedgames.....\mods Prepend means Add. Yup my limited vocab' I had to look it up. So open in Notepad ++ and find {down = device_commands.Button_1, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Pilot Seat'), category = _('View Cockpit')}, Then prepend (add) -- to the start of the line to look like --{down = device_commands.Button_1, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Pilot Seat'), category = _('View Cockpit')}, Repeat for the other 3 lines. Then paste & copy below ( you can leave a few blank lines in between if you choose. {down = iCommandViewCockpitChangeSeat, value_down = 1, name = _('Set Pilot Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 2, name = _('Set Operator Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 3, name = _('Set Left Gunner Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 4, name = _('Set Right Gunner Seat'), category = _('View Cockpit')}, Save as default.lua When you open DCS and UH1 the orange options are gone and you have nice mapping option for whatever HOTAS keybind. Genius !!

Had my Orion 2 for 2 weeks now and some of the above " issues" I have noticed has led me here. Off/ idle switch. Its in the calibration. Set to idle and calibrate from there. On the Simm App Pro it shows when the switches for idle and off are on/ off. They wont work correctly if you calibrate from the Off position. Then in DCS you can map these two positions. Its a case of RTFM which at first I didn't. Doh! Yes the finger lifts aren't too ergonomic and creak slightly. Not a big problem. In VR I also noticed rh moved easier than lh. Bit more tension added. At first to go to AB the finger lifts had to be used. I liked this. However now its bedded in its a push- through and Yes rh goes easier than lh. I'm not sure about real aircraft if this is correct but I'd prefer to need to use the lifts so's I know I'm just out of AB or Not. I do like the realism of needing finger lifts but at $£€¥50 I feel kinda cheated when they cant be used as a solid stop for AB. I have a 3D printer & Fusion 360. Might redesign the AB detent and print my own. Which brings me to.. Yes beware the detent square nut and screw are V short. I too needed needle nose pliers to rescue the nut. Yes it will stay lit when the PC is off if in a USB3 port. . The App Pro software is Ok for calibration but does like WinWing ONLY usb devices plugged in when upgrading firmware. I unplug from my rig and use a laptop. The AG & AA buttons only light if App pro is on. What's that all about ? Still not an issue in VR. Do I regret buying Orion 2 ? Hell no! It's well made, double boxed, solid and configurable to F16/FA18/ Helo. F/A 18 switches are realistic and become 2nd nature when you get going. It cost more than TM's offering but imho worth the extra beans...although I'd think twice about the finger lifts if you already bought without.

I thought probably as much but Steam hacked me off so bad I wiped out all need for it. So maybe change my adivse around. Install OpenXR first and try it. Then if it still gives " Steam critical error" go Standalone. Anybody who's reading this and trys, please post your results.

To any other lost Souls trying to fix yet another " Unexpected Steam Error" issue, VR conks out but DCS keeps running. My above attempts ran well for a while ( months) then came back again and was really unfathomable. Solution ? I moved the whole of DCS from Steam to Standalone. Yes it can be done but only this way. Not from Standalone to Steam. This isn't the end of the issue though. Standalone will still need to use Steam VR to run the headset. So still relying on Steam :¬/ Solution: Install OpenXR software to run the headset instead. Open XR is way more superior and the lighting now with Ver2.8 awesome. No more Steam issues because I have removed Steam from the equation completely. Ok. Steam to Standalone took a weekend. Download Standalone is a big file to download and install by itself. Then "porting" over all the DLC's from Steam also took its time. Not forgetting setup files for joystick etc and non ED mods. Yes it was a B@ll ache because then I had to figure out about OpenXR how to install, use and tinker with it. BUT...Oh its worth it. Think of it as several large obstacles to defeat but take your time, one by one. Once you commit there's no real turning back. There's plenty of "How to's " on the web how to go about this. Steam to Standlone I got from this forum. Open XR turned out way easier than I anticipated. I didn't lose my DLC's and its so much better now. Hope this helps.

GENIUS !!! It bloomin works !!! Ok to the rest of us dipping a toe into icy programing waters. It helps to find the default.lua file in the right menu ( be that Steam or EA Beta Download ) Quote: It's under "...Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick". Copy the file and name that copy default.BAK Click YES to the " possible file extention error." Next open the default.lua with Notepad++ Use "Find" to find the command line iCommandPlaneEject This will take you where you to where you need to add the following command {pressed = iCommandPlaneEject, down = iCommandPlaneEject, up = iCommandPlaneEject, name = _('Eject (push just once)'), category = _('Systems')}, Now I deleted the original "press three times" command and added the above in its place. Save the file & accept file overwrite. Launch DCS and open the Controls page. Now there will be an added controls box of "Eject push just once" Map your chosen key to this. Fly and BOOOM! You can punch-out with just one click or in my case pull of ejection handle. Just dont " Do a Goose " :¬( F14 RIO's should eject the canopy first..then the seat. Check your history here. Looking at the default.lua file I now kind of see how the commands should be set out and used. The pdf on how-to is starting to crytalise. Thank you for your patience LeCuvier. Bravo McNasty_UK

LeCuvier, Thank you for this solution. I went to the trouble of making an ejection handle 3D print connected to a LeoBod board the got stuck at the X3 press. YES pressing a keytop three times is an issue ...if you're in VR. I'm yet to venture into file editing but assume Windows notepad or similar is used to edit the .lua file. Hope to try this soon.

OK I think I've nailed it. I point the finger of suspicion at STEAM version. In Steam there is an option to accept Beta versions. By accepting beta's, Steam downloaded the most current beta version. From here on (3 weeks now) it has been behaving. I subsequently turned the auto beta download option off because it seems there's practically a new one every time you log into Steam. Just running Steam update (non beta) it will report it is up to date. However this is far behind the beta versions listed. Hope this helps.

RBL mode in conjunction with Attk radar (SEA) works. However the SEEK option doesn't toggle. Its stuck at Medium. BOL mode still causes Harpoon to self destruct mostly every launch. With the new Falklands map, recreation of Anti Shipping sorties I think might increase. Please fix E.D

TO CUT TO THE CHASE SEE MY POSTING 6 JULY 2022 Just after the next post I too have just started experiencing this BSOD VR. A lot of faffing around with software settings , MSI afterburner, DCS VR settings made no difference. What did happen today was my TM throttle suddenly needed re-seating as it disconnected. I re-seated all USB's including the USB C to USB B adapter from VR headset to GFX. I've just had an hour of trouble free flying. To me any adapter is a point of fail in my book. I have the HP G2 MkII with the new cable btw. If only they'd made it USB B and had the adapter for laptops instead. Give this a go people. I did also notice that pressing HOTAS buttons would cause the BSOD VR. Odd one. However might explain why other non DCS games ran ok because I was using VR controlers instead. McNasty Uk UPDATE: Well I just found a USB C on the back of my motherboard ( I didn't know was there it was so small). Plugged the HP G2 mk II USB C into it. Seems ok now. As I said, adapters are a weak link. Update 2: Well its back. BSOD VR Tonight I said NO to SRS to run on my PC and its worked ok. I came to this conclusion as IL2 which also uses SRS was playing up. Now I recall, this issue has only been with me since a SRS update. Coincidence? Update 3 Ok its gotten worse but seemed to hang only in mp. I read / googled that- Turn GPU Scheduling off in Windows system\graphics. Or right click desktop and go to screen settings. The gpu scheduling option says it will reduce latency. I turned it off. Just had two hours flight and no bsod in mp. Added to this: on Steam I opted for the beta version download. It rebooted and needed Steam password. My fps seemed to have improved staying more in the 40's. Try it.

Not without a fee. As it goes I'm yet to collate all the files together. There's a lot of prototypes in the folders. All counted there's 15 different parts. Its still a work in progress I guess. If I were to publish, I think it'd need polishing to make a whole better item. Watch this space

DCS UH1 home 3D printed collective, cyclic and center console. Chickenhawk by Robert Mason will light the Huey Pilot turbine in you. Experimenting with your axis curves and good ol flying time will improve your landings. VRS Vortex Ring State is easier to avoid when you've got it all dialed in. The Huey imho is a relaxing ship to fly once you get hours undet your belt. Unfortunately a 1960's aircraft doesn't fare too well against SAM's & manpads as like the latter years of Nam. A labour of Huey love. Took a while from design to completion...3 months but worth it.

If engine #2 starts to spool back, push throttle forward 1/2 and click engine restart. It pushes #2 back over 55% and then catches up. I'm not sure if this is how it's done in real World or what technical issues it would cause but it works.

I confirm same issue. When selecting a previous saved file ( before update) it see's the file but reports " file doesn't exist" Windows explorer confirms file does exist ( phew panic over ) If you tick the input profiles box to "All Files *.* " you can " get around the issue" but its still infuriating.

I'm in for making this too. Controller board wise I use a Leobodnar BU836X USB board. It has 64 bit inputs. Windows only see's the first 32 but fortunately DCS see's all 64. Ok its birdsnest wiring but this board has simple insert holes to bite the wire. Wire I get from "recycling" RJ45 LAN cables 4 lots of 2 pair wire small enough to get into most places. This is my UH1 console which has 120 switches, so I used 2 boards. The collective is Bodnar board again.

I have posted about 4 pages after this. I have had the same exact issue. I discovered my collective wasn't fully down ( in real world). Floor the collective...sorted. Wags replied to my post. Move all control surfaces / axis before starting. Hope this helps.

George has turned Pacifist. He was a killer. Alt 500- 700, speed 50-80 distance 1400m. Now with any weapon he replies "engaging" ...as in conversation with the target we get so close. I put a gunboat in the Kobuleti ponds to see fall of shot. He used to fire but I've noticed if I've set laser range for myself (1200m) it upsets him. I'll try to confirm this and get back.

Thank you taking the time to recreate this. Ok So not so much a bug but pilot error. Although I still cant link too much pitch to no start engine 2 but 1 will. I've reset my axis in Windows too. Cheers. McNasty_UK

Here's my fix to a possible problem of start up on AH64 I found yesterday. Issue: Engine 1 starts to 66% no problem. Engine #2 APU gets it to 24% , flick idle switch ( Throttle now moves to idle) Engine spools to 49% then runs back down. Wont go to 66% stays in the red. My fix was to make sure the collective ( pitch) was to the floor. Then #2 would spool up to 66%. I guess I had pull a tad of pitch. Weird I know but it worked. I have my own 3D printed Collective but basically the collective is on an Axis. I cant figure out if this is a "Feature" of AH64 as in real life or a Bug. I cant see why any angle of pitch would effect #2 engine start up. Huey's engine starts at any collective setting. Ok, its common sense to floor the collective but hey. Hope this helps.