Hoirtel

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?

Thanks, didnt know this! Neither do I, but I am glad that someone has so this may be fixed. But I will prepare to block it.

Will turning off automatic updates be enough to prevent these crashes from happening if/when the v63 goes mainstream? I don't think there is a way to block the app from updating.

I don't have the Tomcat so can't check that one. However I did try the other recommended action which was to remove the super carrier, it now opens every single time! I had a whole carrier group and some statics but worth noting that this is a very old miz which I have updated and changed many times, always been saved in the newer versions but the carrier group I probably haven't touched specifically for a very long time. Next I will add it back in and see how it behaves.

Has anyone else thought that this map has some strange performance issues? I may prepare a bug report (with track) as I consistently see frame time spikes at Nellis. On an empty map these aren't too much of a problem (VR) but add a few statics, even just a small amount of the low poly models and it becomes quite noticeable. For me this is particularly bad when landing on 03 and then making the turn onto taxi way at the end gets stutters, even on a plain airbase. I have seen this for a long time and put it down to the miz file I used (I basically only ever fly this map on this same miz). However after some recent co-op flying and testing on plain maps, I now think there is a problem here. This may also be connected to the more well know issue the F15E has with its radar causing stutters whenever you are flying up range facing toward Vegas. Is this map just too old now?

I'll do that, the mission is one of my own creation, which is still in creation. Which offical mission are you guys loading? I could see if it gets stuck for me. When I first noticed it I did try some other missions and they seemed to work fines, as did a blank Syria map. What was also interesting was saving the stuck file as a template and loading on new miz still got stuck.

Results - First test was to just try opening mission in ME, save, fly - stuck on Sim Poststart. Went into users/appdata/local, cleared DCS file. Back to ME load, fly - stuck on Sim Poststart. Re-opened DCS, load same mission as multiplayer server. Mission loads fine! (Thanks @AKULA_OPTIMUS) Exit mission, went back to ME, load, save, fly. Mission still fine. All appears fixed. Very strange. ....30mins and a few updates later... Stuck on Sim Post Start!! Getting boring now

Only statics & SRS in the mods folder. I did already remove them and try with no change. The file was opening not long ago. The only mod change I did recently was installing SRS. That I had to do because Voicechat is broken. I also ran slow repair and no change. Not been back to try other options yet.

Just found this thread as I have a mission also stuck on SimPostStart. Opens fine in ME, older versions also broken and used to work. This is on Syria map. Plain Syria map loads fine, other map missions I have tried to load also load fine. Miz contains no scripts or mods. I also tried making a static template, which also didn't work. This rules out any of my triggers or drawings breaking it. Must be a bad unit in there somewhere (it has SC). I can see there are various troubleshooting options in this thread and I haven't any of tried these yet. Fingers crossed I have put hours of work into this...

Only if you draw them in separately with the draw tool. Bit time intensive, but it is a workaround.

I agree but we will surely see Vulkan in a 3.0 version? I am all for a single release, considering there is also currently a single and multi thread version of each it can only be a good thing to streamline things. Also considering the massive adoption of open beta, it couldn't ever really be a proper beta.