nzteddy

I don't really get the obsession with civilian buildings. I'll just jump in MSFS if I want to go sight-seeing.

They might be inaccurate, but boy they sound a lot better after the last update. Thanks ED!

Hi, Just some feedback on my impressions reading thru this forum. I do not own this module, but decided to look through the issues before I pulled the trigger on what looks like a very nice implementation. I own the other dcs trainer modules, am interested in this one in particular as it has waypoint navigation. And the cockpit looks gorgeous It looks like you have a core group of loyal supporters active on this forum, and you have been nicely communicative with them. However I fear everyone's patience is being a little stretched given the period of time it is taking to fix some pretty serious issues. For me (even though I don't own the module), these are wrong Nav bearing, Comms n/w with Tacan, AoA not working, and of course the infamous NWS blow-up. I understand it has been christmas break. But some of these bugs were implied to be somewhat easy to fix (eg AoA). Looking at the recent OB changelogs, it does not provide an impression of good triage and prioritisation of issues. Anyway, all I'm trying to say is before the goodwill you have clearly earned with this great release begins to get lost, which it doesn't look like it has yet, I think it would be good to focus on and communicate a plan to address some of these long standing issues. cheers

Latest 1.0.7 yes, and latest OB. Disabled all other mods, and disconnected all my controls, to test Axis Tune out only on Mouse. Still fails with Quaggles, OK without it. Consistantly. Nevermind, there's nothing you can do without being able to reproduce it. Must be something very quirky with my system. I can live without it fine. At least we have it noted in case someone else encounters it.

Hi, I am finding that the Axis Tune dialog does not work when I have Command Injector enabled. I have tested with no input commands at all in place, it still fails. The only way to fix it is to disable the command injector altogether. I use JSGME for this From the dcs.log: 2023-03-13 03:09:54.765 ALERT LUACOMMON (Main): Error: GUI Error: [string "./dxgui/bind/Widget.lua"]:69: Invalid arguments! GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'WidgetSetVisible' [string "./dxgui/bind/Widget.lua"]:69: in function 'setVisible' [string "./Scripts/Input\AxesTuneDialog.lua"]:151: in function 'setFilterHardwareABDetent' [string "./Scripts/Input\AxesTuneDialog.lua"]:208: in function 'setFilterData_' [string "./Scripts/Input\AxesTuneDialog.lua"]:227: in function 'selectFilter_' [string "./Scripts/Input\AxesTuneDialog.lua"]:527: in function 'show' [string "./Scripts/Input\View.lua"]:1785: in function 'tuneAxes_' [string "./Scripts/Input\View.lua"]:2264: in function 'callback' [string "./dxgui/bind/Widget.lua"]:368: in function <[string "./dxgui/bind/Widget.lua"]:363> Anyone else have this issue? Any ideas? thanks

just an fyi. The final version of VC posted with free licenses does not work on the final 2.7 release. Perhaps because the last 2.7 release also had a network protocol change, I don't really know. Anyway, the community edition does work on the final release of 2.7 This suits me personally because I reverted to 2.7 due from 2.8 due to VR performance issues. I suspect I'm not the only one.

ok thanks

Is anyone having issues with the menus and mission editor juddering? Flying is fine.

I have a high end AMD system and G2. I mostly fly low level ground attack ie Viggen. Like most I have spent a LOT of time messing with shaders/mods/settings trying to get DCS to run smooth and look good. In the end I just ran at 45 locked so all maps would run OK. My expectations of improvement were low for what this might do for me. I set aside a full day to set it up, expecting the usual drama with this sort of thing. I cleaned DCS, but kept saved games to compare with the DCS settings I had already settled on. Well bugger me. I had it up and running in 45 minutes. And the difference..OMG what an improvement. Clarity of visuals is hugely improved, and the the ground slides by so smoooothly in Caucasus. The step change is up there with a GPU upgrade. Very very happy. What am I gonna do with the rest of my day? Oh I know....just play DCS...

Yeah I tried playing with clickable data. Didn't seem to change the core behaviour like I hoped.

I want to change the default mouse-click direction of a couple of rotaries in the AJS-37. Normally left-click turns a rotary counter-clockwise. There's a couple in the Viggen that go the other way. Drives me nuts. I understand Quaggles is not the system to solve this as it creates new custom binds. However now that I use PointCtrl custom binds don't help. Does anyone know if it's at all possible to change the core behaviour of controls?

I just look hard left then turn off clickable (mapped to hotas). Leaves the cross out of my fov. Get's around the issue ok until they fix it.

Congratulations on an absolutely stunning effort! You all should be rightfully proud of what you have accomplished May I ask if you have any plans to develop a pilot body? Being exclusively VR, I find a pilot body really adds to the immersion. To the extent I tend to avoid planes without a pilot. I know this topic can be polarising, but just wondering if y'all have any appetite for this enhancement in the future?

Exactly. I switch the pilot off a bit on startup for the side panels, but thereafter have it on exclusively for flight. I hate seeing an empty joystick while flying around, makes no sense.

Hi Heatblur, you are a business, you are only successful by selling more licenses for your modules. While it is true that broken/missing systems are not great, they are typically missed by those who already have the module. I for one fly exclusively VR, and I cannot fly a plane without a pilot. I have tried the F-14 and I love it, but I won't buy it because it doesn't have a pilot. I wonder how many others out there are like me. I hope you are making the right priority decisions for your business.

woohoo! @btd do you think a workaround in the meantime would be to turn oxygen off?

I'd be surprised if a bug that's been around for 5 years fixes itself. @streakeagle were you running 277 when you encountered it yesterday?

@FlappieYes, the track consistently replicates the bug for me. But only on 2.7.6.13436 where it occurred. I tried it on OB, it did not replicate. Unfortunately I don't run 277 as VR performance is too bad for me, so I have manually reverted to 276.

ok, it's happened again. log file attached, seems like lot's of "sound del" events for engines and cockpit right at the end for no obvious reason this time I saved the track, and the replay shows it happening @ 15:04.12 sound bug.logsound bug.trk

Thank you so much - you guys very responsive!

here you go. within the last minute of the flight sound.log

Hi, did you find a solution for this? I too have this problem...

Thanks. Is there a way to tweak the lua file in the meantime, or do you have to enable this capability in code?

The C101 has 5 rotaries that I would like to bind the discrete values to rotary selectors (not encoders). Bomb arm, weapon mode, jettison, vhf mode, nav mode. However it looks like none of them have individual bindings available in the lua file. They all simply have CW/CCW. Are the individual selections available somehow?

You have some interesting concepts here. I too have been down a few different paths with button boxes and how to use them. I'm not sure I understand correctly what you have/propose here. Correct me where I misunderstand please. You have button boxes placed left/right/front, but rather than having them assigned specific controls, they are mouse buttons. You use your head pointer to liven the control, and then use the nearest button box to that cockpit location to activate it, either left/right or wheel. If the above understanding is correct, what I can't quite follow is, why would you need multiple buttons at all then? And what do you use vertical mouse movement for, since you are using your head anyway? I'm really interested to understand your concept properly, as I was about to embark on a new scheme that is kind of a cross between generic/specific. I have a virpil throttle which has the 5-way rotary which I use joystick gremlin to change the behaviour of buttons/switches. I planned to create 3 more diy boxes similar to the virpil, 2 for the front, and one on the other side. I was going to use the mode button to 'select' a operational panel in the region, eg the weapons panel on the front dash of the C101 would be use the front button box , and the buttons/switches/rotaries would operate that panel using proper assignments. So no mouse stuff. But at I would remember how to use the button box for that panel. I always use keystroke assignment, rather than dx button. I find it much easier to get re-usability between modules. So keen to understand your plan before I go down any more rabbit holes too