Jump to content

Lange_666

Members
  • Posts

    3819
  • Joined

  • Last visited

Posts posted by Lange_666

  1. Means you couldn't connect to the ED servers for authorization of your account (probably an issue on their side).
    The topline reads "Authorization is valid for 2d 23h 59h" which means you can play 3 days without being logged in.
    In general these connection problems are solved quickly.

  2. 30 minutes ago, YoYo said:

    You're wrong. When people buy a product, they expect it to work (even without reading forums, posts or searching for it). I guess that's normal? Its also normal in the IT world that when something doesn't work (so critical issue), developers focus on a patch specifically for it (I work on projects so I know what I'm talking about). An example even from Cayberpunk 2077, where, due to major problems, we received the first patch after a week of the entire game. Then it only got better. Here we hear that there is a plan, but nothing is known. This is a critical error, not some guesswork. If it suits you, of course you can live with it, but I know people who tear their hair out and have no technological knowledge because they can modify files without damaging something else and in the future they will have to undo it. This may cause further problems, it is worth adding, because it is already a certain interference. I would also like to note that the status has changed, it was information - resolved internally, and now we have it reported only. The rest regarding changes to the game, new content, etc. can wait a week or two or so, basically it doesn't matter. We are talking about a rather critical issue for many.

    We are on page 20 already. Just keep going.

  3. 3 hours ago, YoYo said:

    You can also see that there are a lot of new people in this topic who registered on the forum only to write that it doesn't work for them. They have 1-2 posts each. This topic, about issue has 19 pages and is growing. Pls think about it.

    That's because they don't read what's been posted here and from people (i don't mention their names but one of them is called YoYo), who post the same complaint over and over again. If they wouldn't do that, it would be just 5 pages and people wouldn't have to go through 19 pages of half crap to find out what the problem and or solutions are.

    • Like 1
  4. 1 hour ago, Saber_Rider said:

    Just a genuine noob question: Where can I get the information when its done?

    Oculus App: Settings ---> General Tab ---> Scroll to the bottom

    2 hours ago, ruprecht said:

    Reverting to the folders kindly provided by one of the pilots here fixed the issue for me, but I don't know how long that will last, or whether Meta will actually respect the "do not auto update" setting.

    If you reverted back to V62 you can now block the update by performing the steps below:

    Simply browse to C:\Program Files\Oculus (or where you installed your application)
    Rename folder \Staging to bak.Staging
    Rename folder \tmp to bak.tmp
    Create a new file called Staging (with no extension, just create a new txt file and remove the extension .txt, then confirm when Windows says the file my unusable)
    Create a new file called tmp (also, no extension)
     
    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.
    • Like 1
  5. 1 hour ago, alfalima2 said:

    I just made this change to the file structure to prevent the upgrade to Oculus ver 63. If anyone is on Windows 11 and struggling with this change because of "Access denied" error, first login as Administrator in Windows, then rename the folders first, create the Staging.txt and tmp.txt files using file explorer. Once you do that then use cmd to rename Staging.txt to Staging (ren Staging.txt Staging) and also for tmp.

    No need to go the CMD road to rename the files, just use Explorer, select the file, choose rename and remove the extension. Then on the prompt that it might become unusable, just hit YES.

  6. One thing that bugs me a bit in your video are the values in the upper right corner.
    FPS seems to be at 120 but if you look at the 2 you'll see another number behind it.
    Same goes for other values.
    Also, for a fixed FPS 60 the frametime should be 16.6ms.
    Yours reed 18.8ms (for 120FPS?) but also there is another number under it.
    Or is that due to the 2 extra monitors?
     

  7. 5 hours ago, Flogger23m said:

    Is this still an issue with Quest VR headsets, including the Quest 2? Is there anyway to not auto updated Meta VR headsets? Or is it mandatory each time you plug the VR headets in it while having an internet connection? If so seems like a massive oversight.

    This is how you can block an update:

     

    Also, when blocking is in place you may see the taskbar blink (or shift if centered) briefly every 5 minutes. This is NOT a Windows problem but Oculus VR Runtime service checking for an update even if Oculus main software isn't running. If you stop it, the blinking stops until the next reboot.

    • Like 1
  8. 1 hour ago, VR Flight Guy in PJ Pants said:

    Thanks, but I have already done that but it still downloads the update... 😞

    That's because the PTC V63 went into release. Turning off PTC will now get you V63 instead of reverting to the V62 since that is not an option anymore.  Blocking the update won't work since it can only revert now to V63. You're too late!

×
×
  • Create New...