-
Posts
5,774 -
Joined
-
Last visited
-
Days Won
495
Everything posted by Vonrd
-
How does the ground hook-up guy prevent electrical shock from static discharge? Is the pole he's using to hook-up grounded?
-
Wow! I'd like to see the crew that's hooking him up. That takes a LOT of trust in the pilot's ability. Almost seems a waste of skill on something like Christmas trees (but I'm sure that he increases the profit margin).
-
Mad skills heli pilot!
-
Student: "Holy crap, I'm going way fast! Maybe this flat lever thingy is the Speed Brake..."
-
Here's the report on Stormbirds: https://stormbirds.blog/2024/04/04/eagle-dynamics-and-razbam-clash-in-public-statements/ Not looking good for the long awaited MiG-23. I hope that they are able to work out their differences.
-
It's been 12 days since I deleted Discord Cache Data and it's already back up to 300 MB. Just sayin'...
-
Awesome! (How many bricks did you step on in bare feet?)
-
Here they are. Put them in your kneeboard for the acft that you want to use to calibrate the PointCtrl. Let me know if you have questions... it can be confusing at first and you do have to close the kneeboard when actually doing the calibration. The cursors won't work with the kneeboard open. Since the instructions are in landscape, you have to drag the kneeboard wider. Watch Miles' video on calibration. You should do the initial calibration on flatscreen / monitor. I don't think I changed much of anything from the initial default settings.
-
I want it! https://www.motortrend.com/news/airplane-engine-1939-plymouth-pickup-radically-radial/photos/
-
Got it and done it. Thanks!
-
BTW. No more crashing. I'm going to try to empty the cache weekly.
-
Can you show the file structure that you used for OVGME?
-
Wondering what's going to happen with this since DCS has merged plain and beta together.
-
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.
-
If I didn't already have PointCtrl I would consider this.
-
It's funny 'caus it's true...
-
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/
- 339 replies
-
- skins
- submission
-
(and 1 more)
Tagged with:
-
Please delete the above post. I thought I could edit out the vulgarity but can't figure out how to do so.
-
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
-
Well done emer landing:
-
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.
-
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.
-
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.
-
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.
