Jump to content

Hoirtel

Members
  • Posts

    1235
  • Joined

  • Last visited

Posts posted by Hoirtel

  1. On 4/17/2024 at 1:24 AM, Darkdiz said:

    Same issue for me, I get around it by copying the Sinai map folder from my game install. I THINK the 2 files you need to copy over are dcs_manifest.bin and dcs_mt_manifest.bin (they were the only ones modified with the patch in this folder)

    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 

  2. 12 hours ago, NemoFlightSims said:

    Meta Quest 2 user.

    After seeing the issue with VR not launching I decided to try something different than swapping Oculus runtime files, which I think breaks some 3rd party programs.  I uninstalled Meta Quest/Oculus software and deleted all folders in %userprofile%\AppData\Roaming.  I factory reset my headset.  I installed the software from the meta website https://www.oculus.com/download_app/?id=1582076955407037.  I closed the program at the login screen.  I then setup my Quest 2 headset with my phone app doing all the initial setup.  I plugged my headset into my PC with my link cable.  I then started the Meta Quest\Oculus software. I logged into my account and saw which version I had from a fresh install it was this. 

    https://imgur.com/WBuG2Qv

    I killed all Oculus processes with the task manager, and turned my headset's Wifi off.  I then went into my Firewall and blocked all incoming and outgoing connections to the Oculus sofware, it looks like this

    https://imgur.com/0ChDV66

    After that my Meta Quest/Oculus software could no longer reach the internet.  It did see an available update(the update that breaks VR) but it would not download it and was stuck at 0%.

    https://imgur.com/msxE8SR

    This allows me to stay on the last viable software version and still play DCS as if nothing had changed.  I don't know if this will help others or not but I decided it probably couldn't hurt.

     

    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.

  3. 1 hour ago, unlikely_spider said:

    Not for me. My experience with my Q3 mirrors yours, where it will lose 10-20% of its charge after 1 or 2 hours of DCS while using link. I'd think it's either the cable or the power delivery from the USB port, but then I'm not sure after the results from your meter test may indicate otherwise.

     

    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. 

    • Like 1
  4. 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.

    1. The switch at the top for mic/PTT/off should follow the same colour coding as the radio mode for ready/off/transmit/receive.
    2. Push to talk should also have PTT in the label, again for parity with the radio mode.
    3. 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. 
    4. 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.
    5. Rename "common" to "everyone"

    Just my small feedback. Anyone that agrees, please thumbs up.

    • Like 7
  5. 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.

  6. 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!

    • Like 2
  7. Just now, slughead said:

    Meta said it’s for ED to fix. So you can assume it does still crash DCS. There’s no way I’m trying it a there will be no way back once you update to the official v63.

    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.

  8. 3 hours ago, Lange_666 said:

    Just block the update as discribed here:


    You'll get a notification that there's an update when you launch the Oculus App but it will be queued until you remove the block.
    This way i know that there is an update but i'll only give it a green light when i read that there are no big issues.

     

    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

  9. 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? 

  10. 1 hour ago, Lange_666 said:

    There is:

    Simply browse to C:\Program Files\Oculus (or where you installed your application)
    Create a new file called Staging (with no extension)
    Create a new file called tmp (also, no extension)
    rename folder \Staging to bak.Staging
    rename folder \tmp to bak.tmp
     
    This blocks the update. When there is an update, you still get a notification that there is an update and that it is in progress but if you check it's queued and the update will be blocked.
    Just reverse the steps and restart the app to let the update go through.

    Thanks, didnt know this!

    1 hour ago, YoYo said:

    I dont use any kidn of beta or public test channel for Oculus software. Its not the first time, where they broke something. Im still on the 62v and no any issue, I hope they will not release this problematic v63 as a public version (after fix ok).

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

  11. On 2/15/2024 at 10:28 PM, Flappie said:

    So far, we used a mission from an official Tomcat campaign. But any stock mission will do as long as it helps reproducing the issue.

    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. 

  12. 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?

  13. 1 hour ago, Flappie said:

    I'm running an experiment with @Nealius: we both launch the same mission and we monitor which files are being accessed thanks to Process Monitor.

    I'm seeing differences here and there, but so far I'm unable to locate the problem. If you want to join the party:

    1. Download Process Monitor archive
    2. Extract Procmon64.exe to your desktop.
    3. Run DCS and, when you're about to load the mission, Alt+Tab back to Windows, and run ProcMon64.exe.
    4. Configure the filter pictured below then click "Add".
    5. Alt+Tab back to DCS and load the mission which gets stuck.
    6. Once you're 100% sure that DCS is stuck, Alt+Tab back to ProcMon, and click File > Save... and save as a .PML file (default setting).
    7. Zip your .PML file and bring it here (you can use WeTransfer or your personal cloud drive, for these are rather big files).
    8. Please mention the mission you were trying to load (official missions if possible, so I'm sure I have them).

    image.png

     

    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. 

  14. 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 

  15. 8 hours ago, rob10 said:

    Do you have any mods INSTALLED?  Doesn't matter if they are in use in that particular .miz or not, they can cause issues anyway if you have them installed.  Removing them would be the 1st step you want to try.

    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. 

     

  16. 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...

     

  17. 49 minutes ago, Schlingel mit Kringel said:

    "Hmm, i love the smell of DCS 3.0 in the morning" ❔ 😄

    This big step of unifying versions at least sounds like we step up one digit.

    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. 

    • Like 3
×
×
  • Create New...