wowbagger

You're right, when I tried to reproduce it a second time, it worked as advertised. Sorry for false alarm. I didn't notice mention of it in the patch notes so I thought it had been missed. Cheers

Just checking that this missed the Monday's patch, correct?

Yep, will do. I wasn't pointing it at you guys, just alerting that it hasn't been fixed yet.

Just had the same thing.

Yes, I did the same. Ran the same mission which crashed before, for a long time and no problem. I almost wish it had crashed . Not knowing what causes it makes me still wait for it to happen again.

All my crashes have been in the Tomcat. These ones were in the PG as I was trapping on the carrier - one happened as I was watching 2 F-18s trap before me. I just did a slow repair, removed all mods, updated the graphics drivers (nvidia), and then left the F-14 circling around the carrier at 2000ft for 90 minutes. No crash. So I'm no closer to knowing what caused it in the first place. Thanks for looking into it for me Flappie. You're the best troubleshooter ED has.

Would anyone be so kind as to have a peak at these crash logs to see if there is any suggestion of what might be causing it? I have been removing mods and scripts (the Way, etc), but it usually crashes after 20-40 minutes in a mission, so it becomes hard to test what the problem might be. Cheers dcs.log-20230725-131432.zip dcs.log-20230725-143706.zip

Awesome, good idea. I can do that. Thanks!

Is it possible to relocate the write folder for the dedicated server to something other than Saved Games, for instance put it on a different drive? Cheers

Latest campaign news here.

It appears as if it's been about two years since anyone from RAZBAM even posted in the bug reports section, so I would be pretty surprised if the S is even in the plans anymore.

Anytime you needlessly limit player options, you are degrading the experience the game can offer. For example, I frequently don't play with headphones on - so no mic. There are two ways to trick Vaicom into allowing the Jester wheel. 1) Get into the Tomcat before activating AiRio with Vaicom. 2) There are three files which if you set to 'read only', Vaicom cannot change them and thus cannot turn off the wheel. Trick #1 is onerous and not worth having to do for every flight. #2 now breaks the Vaicom kneeboard. In any event, using the wheel along with AiRio can apparently de-sync Jester so you end up getting commands you didn't intend. To quote Pene from the Vaicom community discord "It is possible to not suppress the wheel, however it means it will pop up on every command. This is due the way the wheel is implemented by HB. So I guess that was the design decision. I think the solution in the e short term will be to allow the deactivation of each VaicomPro extension via the UI which will give back control and choice to the user." This is why I suggested it would be great if HB might be able to coordinate with the VCP community people to come up with a solution. Simply saying "you don't need the wheel with AiRio" isn't a solution, whatever your personal preferences might be.

Thanks for looking into it. Good luck with ED. We raised the issue of the player's flight plan not being visible on the F10 map (even though you can see all the AI flight plans) a while ago and were told it is supposed to be this way. Despite the fact that it is inconsistent and some of the older missions definitely show the player's flight plan.

Just to add; it would be great if HB could work with the community to find a way that allows the Jester wheel and the AiRio extension to work together, rather than having to choose one vs the other. Cheers

Thanks, was wondering the same thing.

Quick question about the F10 map. With the changes over the past year, do you know if it is possible to mark flight plan waypoints on the map (should someone want to do so) so that they are still visible when the mission is being played? Didn't they add the ability to draw and write on the F10 map? I haven't tried that yet. The kneeboard map is essentially useless and for whatever reason, even with no restrictions, the player's flight plan is the only one that won't show up on the F10 map - and ED have confirmed this is by design . edit: And just to clarify, the things I think should be up to the discretion of the player are labels and external views. Those impact the experience more than any others and I don't see how they can break missions. And if they do break a particular mission, then lock them for that one, but not all. Again this is TOTALLY not directed at Reflected. But others have been insistent on these settings, which baffles me.

Totally agree. Look at how much confusion and frustration it causes. If it does nothing, at least remove it from the settings page.

I guess the point is that ED has no interest in this. I have raised it a couple of times and it has been 100% ignored. So the answer would be for campaigns to come with settings they should be played with, but not enforced. Players can always set their settings to how they want to play, but not if they are enforced. It's really that simple. Another campaign maker responded with something like 'well, some players say they can't help themselves from cheating <sic>, so I force those settings', which is so ridiculous that I have stopped buying their campaigns altogether. There has to be a way forwards so that campaign makers can produce the experience they want to create, but players can get what they want from the campaign they have bought. Overall, in my experience, Reflected takes a sensible approach with respect to labels and such. The blackout thing is a stupid bug that should have been squashed a while ago. But that's another point. More flexible options in the settings allow us to better work around the multitude of bugs which campaign makers and player have to routinely deal with.

Thanks man! I got it figured out. There was a workaround for the Jester wheel being disabled with AirRio activated. It involved simply locking 3 files as read only. This seems to have been broken by the newest 2.8.3.3. However since the files were read only, it wasn't picked up by a full repair with remove extra files ... I guess. Hate not having the Jester wheel. Hollywood seemed to say it was a design decision, rather than a technical limitation (wrong choice in my opinion). I hope the brilliant peeps in the community development can figure out a way to make it optional. cheers

This is exactly what I needed. Many, many thanks for this, and for all your brilliant work on the input injector. You improve the game immensely! Cheers

How is this marked as CANNOT REPRODUCE when so many of us can reproduce it?

The VPC kneeboard works in every other plane, but for some reason has stopped working in the Tomcat for me. It just shows a dark grey blank page. Things I have tried: - remove all mods - full repair with remove extra files (twice) - reset lua - reinstall Vaicom Pro completely (including deleting all it's files in Saved Games and in DCS install) - reset install location in registry using Vaicom control panel - delete other kneeboard images from the Tomcat folder - delete the weird scripts folder that Vaicom creates in c:/ I still get this: I'm out of ideas and going to give up, but I wanted to make sure it's working for everyone else ... just to add to my sense of frustration.

Has anyone found a keybind for Jester Stop/Start talking which could be added with Quaggle's? Sometimes in the middle of a fight he's a real PIA telling me what to do. "I will fire when I'm (expletive) good and ready! You got that? " Opening up the menu in the middle of a dogfight isn't really feasible. Cheers

Thanks much for the update.

I'm in the exact same position. First campaign I ever bought. Kept putting off learning the Mirage while Razbam tinkered. Now wondering the same thing.