bumblebomb

....hence belongs in "General Bugs" - admins, transfer if you want.

Update: a lured a friend of mine into DCS, he started on the F-14 and has that and Supercarrier installed, nothing else, installed openbeta literally Two Weeks ago first time, has no slew mod on his Thrustmaster Warthog HOTAS, no rudders yet and as soon as he puts rudders on the slew it gets marked (!) and stick roll stops working.

All very challenging, yes. Still MS won't get that much active platform control from me. Win10 I can uncable from the internet and it will still run everything that works offline, I don't need to tell MS everything about which program I run when and where and all connected to a personal account. It's not acceptable. Now ED won't have leverage here so I rather posted to make th point and generate awareness. MS better move. It affects businesses and gov't alike. From what I hear they are already in the talks with China and Russia to have versions without the spyway, so maybe there lies hope.

Same here, works when I mark the server "public". Win10pro, open beta.

Hi all, I'd very much wish for a native Linux port by 2025. If Microsoft stays their course on TPM2.0 and MS account being mandatory they will be history to me. I'd even pay. Even subscription based.

Has literally one entry for zoom, that's it. I'll try delete/repair tomorrow when I had time to print a HTML export. UiLayer.zip

I *think* I installed en-US last time and en-GB now, but now perfectly sure. I have a backup of that Windows partition that won't boot anymore but files are accessible. I'll see if I can extract that info. UI Layer: has no axis page! I'll try the delete and send the other zip later, not at the machine right now.

Ok, this is weird: in axis controls, the red markers on the joystick JOY_Y and JOY_X report on mouse-hover "JOY_Y" resp. "JOY_X", see attached photo. When I look into the config files (zip attached) I find references to JOY_Y and JOY_X only in the throttle diff, not in the joystick diff at all. F-14.zip

Sorry I read the entire things and don't see how that helps. I know the structure and diff files.

Installed everything from scratch a few days ago, Windows 10 and DCS open beta right from the servers. Restored config backup by copying in the perfectly working config form a week ago and renamed all USB Device IDs in the filename. F-14 folder, no F-14B, no residue from any other old cruft. Thrustmaster Warthog HOTAS and Saitek Pro Rudders. In controls config in the F-14 (haven't checked others by now) both "chat" options and "mission restart" are marked (!) in the keyboard section, but what's worse both stick axis are (!) as well. Following another post here I deleted the axis assignment for the slew which I use for DLC control and zoom, and the pitch/roll assignment for the stick, restarted the game -- axis cleared. Re-assigned, everything worked: until I restarted the game: exact same situation again. The only difference I can think of: if memory serves last installation was en-US locales, this is en-GB. One other user reporting such an issue in the forums had a big union jack in the avatar - locales issue perhaps?

Installed everything fresh 2 days ago, Windows 10 and DCS open beta right from the servers. Restored config backup by copying in the perfectly working config form a week ago and renamed all USB Device IDs in the filename. F-14 folder, no F-14B, no residue from any other old cruft. Thrustmaster Warthog HOTAS and Saitek Pro Rudders. In controls config in the F-14 (haven't checked others by now) both "chat" options and "mission restart" are marked (!) in the keyboard section, but what's worse both stick axis are (!) as well. Following another post here I deleted the axis assignment for the slew which I use for DLC control and zoom, and the pitch/roll assignment for the stick, restarted the game -- axis cleared. Re-assigned, everything worked: until I restarted the game: exact same situation again. I did not install any drivers for the HOTAS or rudders, and I think last time I had drivers for the Saiteks, but not sure. Will investigate. In the meantime, if someone has a fix or workaround I'd appreciate.

Unlike real pilots I cannot shade off pit elements with my hand. Sometimes the sun makes things hard to read on displays. Now, if a virtual hand would fade in when the mouse cursor becomes active, thus visible, and fade out again when the cursor disappears it would help a lot. I don't even mean a visible hand, just the shadow. Not sure if that's possible as an engine feature or would have to be a module feature. If a fixed object could be in position to the player perhaps?

"Guns guns guns" and Sidewinder tried so far from Training Missions: tutor says "press spacebar to continue", I do, game freezes. *Not* pauses, freezes: jet's standing still in the air while responding to input from stick, throttle, fires bullets and missiles that fly away, too, but stays fixed in the sky. In outside view model gets updated, too, flaps, spoilers, throttles. "Resume" does not help, space bar again fires weapons. Current OB as of 16jan2021.

Whenever Vaicom updates, it messes with my exports.lua, rendering SRS useless until I delete the scritps folder and reinstall SRS. How do I prevent this?

Well, there's always having a gamer laptop with a 2nd license to be your own RIO :) But seriously, IronMike, *I* would pay for an "extended Jester module". I understand it's a hefty job and if it requires more resources, well, call it. The other thing would be beefing up Iceman so we can have some basic patterns like hold orbit or new heading and switching seats becomes viable.

So much this. It's not really the most stylish forum I know but "hideous" is putting it mildly on mobile designs. I fly Hornet, so I can live by hideous, but if it gets in my way I get cross.

All my MP buddies yellow and ambiguous since last OB update. It's sort of a biggie. Not terrible like "crash when pressing button x" or so, but I'd appreciate that to have a top spot on the TODO, if you don't mind.

https://forums.eagle.ru/showthread.php?t=284913 Vaicom not messing with export.lua would be great. I stopped using it because it keeps interfering with SRS, and that's prio.

There's a Pilot-controls-for-LANTIRN mod in the files section btw, if that still works. HB says that will go once Jester can do it, but in the meantime that gives you some laser kitty.

Yes, just a rough status of Jester/LANTIRN would be nice. I know it's a helluva job, not pushing, just curious. But the "right engine" thing being hard to fix should give everybody an idea about the complexity under the bonnet. Coding is voodoo magic and then some. And thanks for the info, my favourite module still after having tried near everything.

Short (1min read) https://forums.eagle.ru/showthread.php?t=284913 Short but in other words: several external programs fight over export.lua. Jeopardizes it every so often. One week Vaicom does not work, the next it's TacView, the SRS... All programs run their own export.lua.programname and happily live together. It's in the API now.

Please. It's like herding dwarves.

With several 3rd party programs hooking into DCS I constantly run into trouble after updates. TacView overwrites it, Vaicom messes with it, SRS gets kicked by other programs' shenanigans ever so often. How about a startup parser that loops over seperate files like: vaicom.export.lua srs.export.lua rsmapper.export.lua ... so they don't interfere?

What greatly helps me in the F-14 is the "tschk-click" the throttle makes when going AB. Boom sounds, noice, but how about a click from the detent finger lifts? If the real ones are not really audible in an F/A-18 just having the event linked to a near silent sound would be only a matter of creating a small mod.

Can you tell us which parts fit in? Like micro switches, 4ways, slew.