Jump to content

Lange_666

Members
  • Posts

    3808
  • Joined

  • Last visited

Everything posted by Lange_666

  1. Why do you even need a Google authorization code to do the stuff you want to do?
  2. Made a mistake in the work order. Just corrected the work order in my original post... -)
  3. 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.
  4. Did you have an older version installed before 2.4.2? I still had 1.5.1 installed. After upgrading to the latest (I just ran the latest installer thinking it would be enough) it didn't work either anymore. Did some investigation it turned out there is another spelling in the TheWay folder (the older one had a space in it) that needs to go into the scripts' folder + the line to copy into the export.lua was different too. After these corrections it worked.
  5. Run the DCS_updater.exe in the DCS World bin directory?
  6. When you move your mouse over one of the Build Slots, you can right click it to set the paths for the DCS directory and for your Saved Games directory.
  7. You can block the Oculus app from updating: 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 shows as queued and the update will be blocked. Just reverse the steps and restart the app to let the update go through.
  8. There is: 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) 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.
  9. That will probably not work for stick/throttle inputs/axis. Windows will create new device numbers for your connected devices. If you copy the old ones over, the old device numbers will not be recognized. Solution is to rename the devices and replace the old device numbers with the new ones that Windows created, then delete the newly created devices. It's the number between the { } like in: Thrustmaster Combined DX128 {1C96BA10-A7EA-11ee-8002-444553540000}.diff.lua
  10. I deleted the dcs_variant.txt in de DCS.openbeta folder, then renamed the install folder to DCS World and de Saved Games folder to DCS. Works fine.
  11. Solved: With the latest version and the new target.tmh stopping a script is instantly again. Still a problem: the position of the windows within Target Script Editor is not solved. Device Analyzer in Target: not a single Thrustmaster device to be seen, nor a combined one when a script is running.
  12. Nope, I have that also. For that reason I don't use the push-in function.
  13. If your new RAM sticks are of the same specs as the old ones (speed and timings, size doesn't matter) you can use the old ones together with the new ones giving a total of old + new. Mixing RAM sticks with different speeds and timings is not a good idea.
  14. For what I read, it seems that when starting DCS from the regular DCS desktop icon it now starts the MT version versus starting ST like it did before. (I use SkateZilla's updater/launcher where I have the option to launch either in ST or MT). To be sure you launch ST, just go to your DCS install location, in there you have a directory called bin and another bin-mt. The bin is ST, the bin-mt the MT version. Both contain a DCS.exe. Just go into each and create a shortcut from DCS.exe and put these on your desktop. Rename one DCS-ST and the other DCS-MT. This way you can launch either ST or MT and see the difference between the two. As Silverdevil says, the best thing to do if you want to use your old RAM, is to get exact the same specs (brand + RAM timings) as you have installed already. If you mix brands or use add a set with different timings you can easily run into problems. If you can't get them anymore, replace your old rams with new ones. Also, be sure how many RAM slots you have. RAM always comes in 2 pieces. If you only have a motherboard with 2 slots, you can only replace with new RAM. 16GB is on the edge these days for DCS. With settings too high I go over 16GB Ram on a simple mission, in VR multiplayer it uses even over 32GB.
  15. Might be an option if my current Rift-S dies but I'm preferring one with a DP connection instead of wifi/USB-link.
  16. RGB noise: Could be the cable Pico: Overall clarity is better but there are so many ghosting artifacts when the image moves quickly while using ASW. Without ASW at native refresh freq it was very good but it was difficult to keep the FPS above the native refresh freq on my setup (5800x3d+3080Ti). Once it dropped below that it started to stutter. And since ASW was so bad i did send it back. ASW also only worked with Virtual Desktop, with their own Streaming Assistant it even didn't. So i preferred a headset with less resolution but with a lot better overall performance.
  17. Thats what i ment. Was more in an answer to YoYo because he's impatient...
  18. Rift-S (since that was what the topic was created for): I still use it (although on half the refresh rate through ASW). Think it's a good headset but i only have (had) a Pico 4 to compare it to and i prefer the Rift-S over the Pico simply because it has a display port. The Pico has too many artifacts when using ASW (or it's implementation of it) compared to the Rift-S. Biggest drawback for me of the Rift-S is the disconnection (not being recognized) each time the PC has been shutdown. So i need to un-plug / re-plug the USB each time after a PC restart. I had that also with my previous headset on my previous PC but there it would only disconnect 20% of the reboots and even then simply stopping and starting the Oculus service would make it re-connect. On this PC my first Rift-S never disconnected but my second one does disconnect each time and cycling the Oculus service doesn't do the trick with this one. So it's a bit headset depended.
  19. They should also look into their device analyzer. In the previous version i still had the combined Warthog showing when a script was running. With this version nothing anymore, no single unit, no combined one but... it still picks up my MFG rudders...
  20. Thanks for the info. Cool that I don't have to use the target128dx hack but it doesn't solve the above problem. This is how the latest Target version looks after it's started so that's not solved: I can drag the status window down and the script window to the left but after closing and restarting they are back in the same place as the screenshot below shows. Also, stopping a script still isn't instantly like in Windows 7, 8 and 10 but still varies up to 15 secs (in recent days i saw it stop once directly). According to Thrustmaster this is some sort of incompatibility of Windows 11. This update didn't solve that. I had the same behaviour as below after an update from Win 10 to 11 and also after a complete fresh install of Win 11 Pro.
  21. OpenXR Toolkit: https://mbucchia.github.io/OpenXR-Toolkit/
  22. Time to block the update of the non PTC version because when this bug enters the release version, we're screwed.
  23. Yes but then you would see the shadows created by the cloud move rapidly as the cloud passes in front of the sun. Here it's like an extra cloud layer is added or shifted at once. This is visible to the left of the HUD when it happens.
×
×
  • Create New...