#Extension of behavioural issues using Wemod overlay shortcuts.
1 messages · Page 1 of 1 (latest)
Hey @rare topaz Thank you for reaching out about this. Does the game offer any custom keybinding options that might allow you to switch from fullscreen to windowed mode?
No , I forgot to add that it locks the mouse from selecting menu options.
Thanks, Do you own the game on steam or ea?
Steam , same specs as before
For what it’s worth running the game on ultra with dlss on quality no ray tracing and at 4K
Thanks for that info. I’ll send a report to the team for testing so we can see if we can replicate this issue. In the meantime, have you performed a clean reinstall of the app recently?
- Use Add or Remove Programs or Control Panel to uninstall Wand.
- Find and delete these folders:
-C:\Users\Your_Name\AppData\Local\Wand
-C:\Users\Your_Name\AppData\Roaming\Wand - Restart your PC.
- Reinstall Wand by downloading from: https://wand.com/download
Nope but there has been a wemod update since
Pleasure
does your app still say wemod?
Nope wand
Hey LivelyRainMomo, Hope you had a great long weekend! Just following up we heard back from our testers, and after spending over an hour in game, we weren’t able to reproduce the issue. We tested across different resolutions and quality settings as well.
It’s likely that a third party app or something on your Windows setup is interfering. I’d recommend turning off any unnecessary startup apps, restarting your PC, and making sure no other overlays are running before trying again.
Definitely not a third party app due to the fact it’s only on very specific games and can’t be replicated on any other game besides I tried and the issue persisted
I even turned off everything non essential restarted the pc to kill all processes and still the issue persisted but only persisted when wemod ran , not nexus mode etc
Sorry I didn’t get a notification of your message
No problem. I’m not 100% certain either, but it’s possible a third-party overlay (Steam, NVIDIA, etc.) is causing interference. I had a second tester review this as well and we still weren’t able to replicate the issue.