Hoirtel

So I think I cut too much, nothing seems to work properly. I have restored to a fresh profile, but cannot disable commands in batch. Is there any quick advice you have for making the F4 commands only the crew chief and jester? Sorry - hate to ask you to help undo all your hard work but these aspects are so good and the others conflict with my own profile.

My experience with VoIP issues recently have all been down to client config. Somehow people just don't seem to understand it, and can't get their head around the three or four buttons they need to bind. I have had people say they prefer SRS "because it's simpler" when I point out the whole separate application with separate bindings, and pages of settings and options. I think VoIP needs a wizard to help those that for whatever reason, just can't figure it out. I say the above because it comes out sooner or later that "oh I didn't bind X" and then suprise suprise it we can speak!

Thank for your help! After rebooting the PC I was able to fully access the profile.

Thanks @Bailey for these great profiles. However I am wondering if there is any way I can disable/delete the cockpit and DCS commands? I realise that I can just jot use these but I have found that there is overlap with my own DCS game commands, and also some room for error. For example yesterday I had a misrecognition with the auto shutdown mid flight (F4). I would like to improve my flight safety by ensuring this isn't possible! Also as I would like to use some others I think there is overlap between them. I did try to open the edit window but as soon as the DCS control category was on screen voice attack seems to go unresponsive? Never had this happen before. Task manager hasn't said it's unresponsive but I have been unable to interact with it. I think I probably do not need the 870 commands in this section. I would happily pay for a version that is AI controls only. Started up the F4 yesterday and absolutely loved doing it by voice! Thanks again.

Hello, I am hoping that somebody might be able to help me with troubleshooting my home made button box that has rotary encoders. The problem is that these encoders are all available and bindable in the controls menu, all seems to work well. Once I get in cockpit I find that most of them do not function in some modules. Its very odd. Many of the ED modules work all the time - apache being one of these. The modules that don't work so far are av-8b, F15 and F4. I don't always use them all and not always flying all of the modules but this has been repeatable enough now to know for sure. I had thought it might be a razbam issue until I realised the F4 is having issues too. The box is made from a leo bodnar 32 button board, and I have configured the firmware to accept encoder inputs. The encoders are the cheaper ones that do not have the small PCB on the base, I am starting to wonder if this is the problem as I have read some things about signal cleaning but I thought the leo boards did this anyway. Perhaps there are too many wires stuffed in the box? Could that be an issue? Could the leo bodnar board also be the issue? I have another of the same board with push buttons and switches and while i wouldn't say it is faultless it works 99% of the time. Hence why I think I may need better encoders. Any help greatly received. I am ready to fix/rebuild but not sure what to do

Just scrolling through this thread for interest/learning. Are you recommending that server owners do not forward the GUI port 8080? Just access locally instead.

No additional port forwarding required. 1st thing to check is that voice chat is enabled in the server options, under the advanced section. Then once you can open the window it should basically just work. Been pretty good for me recently

Anyone know if there are any air to ground training ranges located on this map?

Looks awesome. A version that can be used in co-op would be amazing, there are important data link skills that can only be done in MP

Potato banger.... ...45mins I think it was..

No this is definitely incorrect!! The way to install is to use the command line. It seems to me a bit of an oversight that all maps bar this one are available during initial install hence why I raised the issue. The command line process is very easy once you have found the command required. Nobody responded to me on this post so I did find it elsewhere in the forum. Go to the bin folder and open a powershell window there. Then paste in the following: .\DCS_updater.exe install SINAIMAP_terrain

When I have gone to download DCS dedicated server I notice that the Sinai map is still not on the map tick list at the beginning? I know it can be downloaded with a command but seems like it is just missed off this list? Can someone also remind me of this command otherwise I will need to trawl through the forums again.

Yes - 2 weeks x3

Blocking via the firewall! Good idea. Wish I thought of that. I unsuccessfully tried renaming the folders as described many pages ago... And it still updated, just happened yesterday. Personally I will have to wait now. I have other things on the PC that need my time, but wish I had seen this last week.

Yep same for me. Roughly 3 hours is usually around 25% battery drain. Link cable plugged into x670E. Pretty sure the variances are down to what the usb port delivers.

I enjoy using the voice chat and I hope it gets even more uptake across the community. Having used it with a few other people, including some for the first time, I have a little feedback about the GUI in Lobby, as I think it makes things a bit confusing. Lobby mode is a real strength to DCS and something that SRS doesn't really provide. The switch at the top for mic/PTT/off should follow the same colour coding as the radio mode for ready/off/transmit/receive. Push to talk should also have PTT in the label, again for parity with the radio mode. The green radio antenna icon for switching into lobby mode, should be removed completely and replaced with a sliding switch that says "Lobby" and "Radios". Everybody seems to look at this symbol as a connected/not connected indicator. Each room should be a separate box, just like the radios. Each box should have a small button that says "join" and when joined it can say "current" and the whole box can be a brighter colour. Again like the radios. This would of course be in addition to the persons name being listed in that room but some don't realise the way it works and at that point, you can't talk to them! The current system of bold titles is really easily missed if the rooms are not expanded. Rename "common" to "everyone" Just my small feedback. Anyone that agrees, please thumbs up.

I used to use the hand tracked quick menu on my quest 3 all the time, very handy for accessing the recording feature among other things. For the last little while it has stopped being available in the link menu and in DCS and I haven't figured out how to get it back. Anyone know where this option is? I'm on v62 running over link cable.

I think I would be right in saying that there isn't ever module launches during a sale... so...

Its so hard to troubleshoot voice chat with individual people, never quite sure if the issue is with either client or server. Is it possible to get a test bot enabled? That way each client could go off and individually check if the bot can hear them and they can hear the bot. Perhaps just a GUI representation of a lobby and a radio. I assume these are done differently has prior to last patch the radio modes broke entirely while the lobby still worked. I know there is the mic test, but not sure that is doing the same thing, as I have just finished a session with total broken comms, couldn't hear either of us in lobby or radio. But the mic tests were working.. I could see the other persons' green speaker lighting up and we could see the radio transmissions coming through. I have used voice chat with with others recently so I know it has worked, but just can't quite figure out which of us needs to go off and mess about with settings!

Yeah, fair enough. I suppose there is a chance that it may have been inadvertently fixed. I guess we will find out at some point. I think I have done the block, didn't have the two folders so I made them. Not sure if I need to create generic "files" within them.

Do we know if the new PTC also crashes DCS?

Just checking, you say create a new file called staging with no extension, but then rename folder? Do you create a folder called staging? same for tmp

No, I used the leo config software to change the second to _2. It is similar.

--force_oculus_VR did work for me when I tried it. Confirmed by openxr menu not displaying. I also have a foveated rendering and super sample applied in this tool which also did not load. I haven't kept using it as still on v62 but thought I would check it to make sure I could do it.

Hello, hoping someone here might be able to help with a strange issue I am having. Not so long ago I made a home controller with a leo bodnar board, this is a box with 8 rotary encoders, all with push. This is the second controller I have made, with the first all switches and I made some time ago. I can't say when exactly the issue happened, or if it hasn't always been present, since I do swap airframes a bit. So this controller is working as expected in windows game controllers options, and works as expected in all module controller binding screen. The really odd thing is that is some modules, only two of the controls work? In the apache and hornet, they all work as expected. In the harrier and F15E, F5 only two work in cockpit. Totally bizarre. The harrier I also have two push buttons on the other leo board do the same thing, and in the F15 one half of my middle cougar thrust master screen also does not work, although sometimes it starts during the flight. I really can't work out what would be the source of the problem? I have focused some trouble shooting on the main rotary box where I tried removing and re-adding it and also moving it from USB hub (powered) to a native mobo socket. No change. The affected aircraft controls do work when rebound to a different switch on another controller (throttle/other box). I wondered if it was the way I built it, or something to do with the components but why would it works so flawlessly in every single control menu and in some modules? I wonder if I now have too many controllers, but I doubt is is more than a full home simpit?