Jump to content

Vonrd

Members
  • Posts

    4,935
  • Joined

  • Last visited

  • Days Won

    296

Everything posted by Vonrd

  1. I want it! https://www.motortrend.com/news/airplane-engine-1939-plymouth-pickup-radically-radial/photos/
  2. BTW. No more crashing. I'm going to try to empty the cache weekly.
  3. Can you show the file structure that you used for OVGME?
  4. Wondering what's going to happen with this since DCS has merged plain and beta together.
  5. Discord kept crashing on me tonight. Google brought up these recommendations: In Discord, navigate to User Settings and click on it. In the left pane, scroll down to Appearance. Then in the right pane, scroll down to Hardware Acceleration and make sure it's turned off. Delete Discord app data. Press the Windows logo key and R at the same time, then type %AppData%. Go to C:\Users\Whoever you are \AppData\Roaming\discord\Cache\Cache_Data and delete everything in there. It was HUGE... about 1.8TB (yes, I'm exaggerating, but it was very large) . I'm hoping that this works. Due to the enormous size of the Discord cache, I'm hopeful and think that it should be a regular part of housekeeping.
  6. If I didn't already have PointCtrl I would consider this.
  7. It's funny 'caus it's true...
  8. Depicting Fw190A-3 Wk. Nr. 313 of Stab III./JG2, flown by Adjutant, Oblt. Arnim Faber who after shooting down a Spitfire flown by by Sergeant Trejtnar of 310 Squadron (Czech) RAF mistakenly landed at RAF Pembrey in South Wales on 23 June 1942. Includes three versions, two in Luftwaffe markings pre-capture (Luftwaffe markings has one with and one without swastika) and one post capture after being repainted in RAF colors / markings and given the RAF serial number MP499 and a 'P' for prototype. Interesting that they retained the "Fighting Gamecock" emblem of III./JG2. Link: https://www.digitalcombatsimulator.com/en/files/3336379/
  9. Please delete the above post. I thought I could edit out the vulgarity but can't figure out how to do so.
  10. original link: https://www.reddit.com/r/Shittyaskflying/comments/1bfwj5h/i_just_made_this_new_ercraft_what_the_fuck_should/?utm_source=embedv2&utm_medium=post_embed&utm_content=post_title&embed_host_url=https://forum.jg1.org/index.php
  11. Well done emer landing:
  12. According to yoadknux and several other people: I'm happy to say that since I've written this post, my Meta Link App Version remains at 62, and everything works as it did before. So, if you follow his instructions exactly you might not have to keep re-installing.
  13. Seems that this from yoadknux has worked for several folks: Posted Monday at 11:15 AM For now, I was able to survive the dreaded 4 hour snooze. Here are the steps I took. 1) Uninstall Oculus with the regular Windows uninstaller. 2) Go to C:\Users\(your username)\AppData and remove all Oculus folders inside Local, LocalLow, Roaming 3) Install Oculus from the following link: https://www.mediafire.com/file/rn5uurwqvv9qp8q/OculusSetup.exe/file - This will install v62 (at least at the moment this post was written). 4) Turn off Automatic updates on the Oculus app settings. You will still get notified that there is an update ready to install. Snooze it. 5) Go to Oculus folder, delete all the contents of Staging and tmp. Make a copy of the entire Oculus folder, name it Oculusv62. 6) 4 hours after the snooze, the app will update to v63. Once it's updated, go into safe mode, and replace the contents of the Oculus folder with the contents of Oculusv62. You can do this by deleting the Oculus folder and renaming Oculusv62 into Oculus (I recommend keeping a copy of Oculusv62 regardless) Optional: Also make a copy of the Oculus folders inside Local, LocalLow, Roaming (from step 2). 7) Exit safe mode. Run OculusSetup, and use it to repair. The outcome is that you will have a "fresh" v62 with empty Staging & tmp folders, with auto-updates disabled at the oculus settings. I'm still not 100% sure it works long term - it only worked for a few hours for me. It may still update to v63 somehow. However, if it updates, I think restoring the Oculusv62 + AppData folders should send it back to v62 for another few hours. Good luck guys. And I hope ED fixes this issue as soon as possible.
  14. We got a surprise on our tax returns, more than we expected. Karin bought a new iPad Pro and I just ordered the Pimax Crystal Sim (after doing several days of YouTube-ing and forum research). Considering what I've found, I'm slightly worried but also excited. I'll let y'all know how it works out.
  15. One of the latest from Bignewey We are working with many modules, and the core of DCS, we are already merging and testing fixes for a larger patch. I can not give you a date yet for that patch as it depends on test results for the whole of DCS. I am sorry but its not as simple as you think it is, so we will need to be patient. Again, we changed nothing in DCS, meta's update created the problem. thank you I would think that since a sizeable portion of ED's customer base is affected and, it seems, unable to use it's product (many report the recommended work around not fixing anything) that coming up with a fix, even if temporary, would surpass all other work. As to this statement: we changed nothing in DCS, meta's update created the problem. Guess what Meta's response is? If the issue is only happening with this one game, then you may need to reach out to the game developer and ask that they make the game more compatible with Quest devices. The dueling blame game... and who's the bigger dog in the game? Still, as BN says: [the fix,] its not as simple as you think it is.
  16. Just saw this: 7 hours ago, BIGNEWY said: I have no date to share for the next patch at this time. Patch cycles on average will be every six weeks, it just depends on development merges and testing. That's BS! Six Weeks! I think some stink should be raised but since I'm not affected I can't justify getting on them personally. If it does turn out to somehow bork my G2... That's piss poor customer support more akin to Jason at his worst IMO.
  17. Reading through the Hoggit it's been said that ED is aware (how could they not be?) but will not do a Hotfix and will address it at the next scheduled update. If that is actually true maybe EVERYONE should post tickets with support and flood them. Hopefully Bignewey, et.al. will post something tomorrow.
  18. This scares me bad: Apparently this is an OpenXR feature change. All platforms needs to update it to remain compatible. "One caveat: WMR It is deprecated so WMR as endpoint will not get it (MS stopped working on it). So when ED makes the change in the next patch bye bye Reverb G2. DCS will not run on it anymore probably." However, my G2 worked fine tonight. I'm seriously considering a Pimax Crystal.
  19. More on Hoggit. Looks like it affects all the Quests...
  20. Oh Man... that's B.S.!!! I wish all these tech giants would make ALL updates optional. They already got our money. It seems that they are breaking stuff to move our hardware into early obsolesce and force us to buy new stuff. (Yeah, I realize that's kind of a tin foil hat statement but still... ) I hope ED steps up to the plate and gets a fix pronto. Meta certainly doesn't give a sh*t.
  21. If you have any interest in WW1 you might consider FC also. Several of us are currently flying some events in FC.
  22. This is one of the maddening things that DCS does. It assigns things that it "thinks" are needed. Whenever I get a new module I find bindings assigned for stuff that I never put in. I always clear out everything for all devices except the keyboard. Then I do my bindings. Very occasionally, I still find spurious assignments. Usually after an update or repair.
  23. We have "Flying Humor". I thought I'd start a general RL Aviation post. This could have been bad. I wonder who changed that wheel last. He / she's in for some sh*t.
×
×
  • Create New...