Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
sup dude im having the same problem at the moment as well, not sure it is if its steams/uplays/or geforce breaking something or something broke in the most recent update or geforce driver
i have a way of playing the game but you wont be able to have your discord overlay showing, you have to run R6S as administrator to be able to play, hopefully this helps and hopefully this gets patched soon
tried a lot of things and nothing seems to work for me so far.
reinstalling siege, reinstalling uplay, setting rainbowsix.exe to admin and starting directly from the files, setting compatibility mode on, rolling back to the previous nvidia driver, updating directx, verifying game files
all of this done multiple times
literally nothing works
EDIT: so i may have found something that works... not sure but it seems to work for me atm
i always have my ds4 controller plugged in along with ds4windows active.
i tried quitting ds4windows and siege starts up now.
interested if this helps anyone else
yeaaa nvm it was just a fluke
-fullscreen and save then relaunch.
It will force game to open full screen and usually stop this dumbass behavior
ok so ive found a solution that is somewhat reliable so far
i use a laptop and the thermals on here get insane when gaming so i lower my power voltage with intel XTU to prevent thermal throttling and what seems to work is that if i give it a little more voltage(+0.010v<=) before starting siege, it tends to run properly.
another thing is that maybe affects the startup is firewall or antivirus stuff, in my case it was malwarebytes, so i put siege in the exclusions list and that also seemed to help.
clearing my memory cache also helps sometimes
it also seems like my controller doesnt effect the startup anymore for some weird reason
sry for the long post but these are the things ive tried and seems to work most of the time, still not 100% but close
Sorry to hear you are experiencing this strange bug.
Have any of you made a ticket on our website?
{LINK REMOVED}https://support.ubi.com/en-GB/
If not, please do so and include your MSinfo and DXDiag files so I can forward these over to the dev team to take a closer look at what could be causing this. If you are unsure on how to generate these files, please refer to the link below:
{LINK REMOVED}https://support.ubi.com/en-GB/faqs/000023904/How-To-Submit-Dxdiag-MSinfo/
Thanks
- Support