vandijk84 Posted August 31 Share Posted August 31 Hello. When I want to play BO6 and search for a game it doesn’t load me in a game. If I search a game with my stock router it loads in a game. What can I do to load in with my r3? Or does it need an update for the game? Link to comment Share on other sites More sharing options...
brufen Posted August 31 Share Posted August 31 Add your device in DMZ “mind you just to test if it’s a port or another issue” by going to setting>DHCP>Reserved IPs. Once added add go to GeoFilter and add your device then pin point your location on the map and pick whatever radius “or use my location on and pick your radius on the map if you want a better connection. There are other aspects. It works smoothly for me and black ops 6 Beta and used it with steam or XBOX pass versions “both on PC”. good luck Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 31 Administrators Share Posted August 31 You could try the above but otherwise you may need to disable the Geo-Filter for the moment while we test it and hopefully get a cloud update out during the beta period Link to comment Share on other sites More sharing options...
SouthernGypsy Posted September 1 Share Posted September 1 Something is strange for us for sure, in the beta our Geo-Filter does not seem to be working at all.... We have the XR1000v2 and have our Geo-Filter fence setup so we almost always go to the CoD Dallas, TX dedicated servers where our latency is always in the low to mid teens (11-17) but ever since the beta we have been getting stuck on a sever in JAPAN every single game even with the Geo-Filter set to strict mode which results in latencys that the best we have seen was 158ms, but the games are often 200+, and sometimes 300+ and the game sucks because of it. Oh, and if I click on that server in Japan, it will not allow me to DENY it, the DENY button is greyed out. Gotta love poping a guy who was standing with his back too me doing something with his kill streak and not moving and I shot him 3 times dead center in his back with a 1-shot kill sniper rifle from 50 yards, and THEN he turns around and kills me with an SMG that showed he killed me before he ever even fully turned toward me and had never even raised his gun on my screen. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 2 Administrators Share Posted September 2 Could you provide the ID of that Japanese server please? It sounds as though it is whitelisted which is why you keep connecting to it despite your settings and can't deny it. Once we remove that it should stop that behavior. Link to comment Share on other sites More sharing options...
SouthernGypsy Posted September 2 Share Posted September 2 9 hours ago, Netduma Fraser said: Could you provide the ID of that Japanese server please? It sounds as though it is whitelisted which is why you keep connecting to it despite your settings and can't deny it. Once we remove that it should stop that behavior. It looks like there may be more than one of them at that same locaiton but here is a cust and pate of the last one when I manually pinged it while a game was going (one odd thing to note is the DumaOS says we're pinging it at 17ms which is hard to believe from Arkansas to Japan, in game it's always 160+ as I mentioned earlier. If I go to the Heat-Map and ping a Japanese server there in what looks like the same area we get a ping of 168 which is more consistant with the best pings we see in game during the beta matches ; Ping Ping 17 ms Host Type Dedicated Server ID 93231be6c032d0d5 Domain Name 230.50.213.35.bc.googleusercontent.com Name 0/20 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 3 Administrators Share Posted September 3 Thanks for that, I'll pass it on, most likely we're unable to ping the server (game servers don't generally respond well to pings) and so it's taking the last ping response which is low. Link to comment Share on other sites More sharing options...
SouthernGypsy Posted September 6 Share Posted September 6 On 9/3/2024 at 9:33 AM, Netduma Fraser said: Thanks for that, I'll pass it on, most likely we're unable to ping the server (game servers don't generally respond well to pings) and so it's taking the last ping response which is low. Well the final day of the last Beta on Block Ops 6 we was finally getting a server that looked like it was in West Virgina and sometimes on in Ohio. Then today you guys released a map advertizing the new R3 and even mentioned BO6 and had the map showing all the US servers. Plus we are getting pings in low teens from one in Dallas and one in Las Vegas (not even shown on your map but it shows as a dedicated server) and yet when we went to join a game, right back on the Japan server Again. It sees the ones much closer to us, it shows they are much lower (low teens) latancy, but go into a game and your 160+ latency and on a Japan server... Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 6 Administrators Share Posted September 6 We're testing a cloud update currently, I appreciate it's not ideal during the beta to have it not work correctly but we only have limited time to test it - even less so given working hours, we don't commit to having full compatibility during the beta because it's always subject to change but it does allow us to have day 1 support on release. If it's not working well for you currently best to disable the Geo-Filter and enjoy the rest of the beta as much as you can prior to release. Link to comment Share on other sites More sharing options...
SouthernGypsy Posted September 7 Share Posted September 7 5 hours ago, Netduma Fraser said: We're testing a cloud update currently, I appreciate it's not ideal during the beta to have it not work correctly but we only have limited time to test it - even less so given working hours, we don't commit to having full compatibility during the beta because it's always subject to change but it does allow us to have day 1 support on release. If it's not working well for you currently best to disable the Geo-Filter and enjoy the rest of the beta as much as you can prior to release. Oh I udnerstand, but I found one oddity. We ususally have our Geo-filter in the Polygon mode (and it covers two of the US servers we see) but it ALWAYS goes to Japan, we switch it to the circular mode and even though its set to cover the same area (certainly those severs) it works more often, have played more now and have been on the WV sever a few times now but still the occasional Japan one. But in Polygon mode its ALWAYS Japan. If we turn it off it's ALWAYS Japan. Link to comment Share on other sites More sharing options...
SouthernGypsy Posted September 7 Share Posted September 7 I updated my Geo-Fences lay out in Polygon mode and it looks ok, remembers the shape when I restart. But to be safe I hit the RESYNC CLOUD button and everytime I do I am getting the following pop-up error message window that I don't know if it has anything to do with my new shape or not, I swapped back to the circular mode and tried again and still get the same error. Error: RPC error 'ERROR_UNKNOWN': invalid key to 'next' -> stack traceback: ?: in function <?:73> [C]: in function 'reply' ?: in function <?:370> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:334> [C]: in function 'run' ?: in function <?:427> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:268> (tail call): ? ?: in function <?:39> [C]: in function 'xpcall' ?: in main chunk [C]: ? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 7 Administrators Share Posted September 7 There should be a cloud update to fix it so we're ready for day 1 release. Could you try the resync again and see if the same error comes up? Link to comment Share on other sites More sharing options...
SouthernGypsy Posted September 7 Share Posted September 7 41 minutes ago, Netduma Fraser said: There should be a cloud update to fix it so we're ready for day 1 release. Could you try the resync again and see if the same error comes up? Just tried it, still same error. Will try again tomorrow. Oh, also wanted to report that when I go to the Ping Heatmap, there is a Server that shows to be in Las Vegas, Nevada but when I looked closer I noticed it's ping times was always almost identical to the Dallas, Texas server. So I clicked on the server that was showing to be in Las Vegas and sure enough, it said it was "Black Ops 6 - Texas" and shows the same IP address as the sever that is in Dallas, Texas. In the report list at the bottom of the screen it also says it's in (GMT-0500 Central Daylight Time) which Texas is in, but Nevada is in the Pacfic Time Zone. So I believe the software (certainly on the Ping Heatmap anyway) has the Las Vegas, Nevada server confused with the Dallas, Texas Server. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 7 Administrators Share Posted September 7 What firmware version are you on currently? Thanks very much for the report, I'll pass that on to be corrected. Link to comment Share on other sites More sharing options...
SouthernGypsy Posted September 8 Share Posted September 8 6 hours ago, Netduma Fraser said: What firmware version are you on currently? Thanks very much for the report, I'll pass that on to be corrected. XR1000V2 1.1.0.16_2.1.25 Today the RESYNC CLOUD is working again without the error coming up. So maybe they was working on it or the cloud it syncs to was down last night but whatever was causing it I know it lasted at least 10 hours... Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 8 Administrators Share Posted September 8 6 hours ago, SouthernGypsy said: XR1000V2 1.1.0.16_2.1.25 Today the RESYNC CLOUD is working again without the error coming up. So maybe they was working on it or the cloud it syncs to was down last night but whatever was causing it I know it lasted at least 10 hours... I think it was a bad cloud update, some weird things were happening on the R2 as well, once removed it resolved them. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now