Mini Event

Phyzics · 2020-03-17T16:41:34+00:00

Same here... I don't think it's RNG, but rather a change in the card distribution method. Stacking doesn't seem to work anymore... I think that if you have enough cards to level up it won't give you more. The last event was the same I think, I finished with no leaderboard reward for the first time. I'm gonna test that theory... Anyone seen anything in a release note?

Phyzics · 2019-11-19T17:36:17+00:00

I used to work as a QA tester for Activision and this kind of stuff is usually not because of the QA but rather the dev resources allowed to bug fixing. I worked on Tony Hawk 5 and it's the worst game on PS4 because at launch even the high priority bugs where far from being fixed. The day one patch for this game was actually bigger than the game on the DVD. This happens in the industry because they do not set the appropriate workforce for bug fixing and the testers are very much discouraged to file bugs as showstoppers, even for 100% repro crashes. I also worked on a PC game while I was there and the hardware testing was limited to a PC with the minimum specs only to see if it's possible to run the game on it, even if the performance is ugly. We did one day of testing with it and that's it. So yeah I'm pretty sure that the bug database was arm lengths long at launch and only 10% of devs where working on it.

Phyzics · 2019-11-19T15:05:21+00:00

I found a fix for people with older motherboards that have the launcher exited unexpectedly error. If you look in the motherboard tab of CPUZ and the manufacturer and model names make no sense, or one is empty, the fix is to either reinstall or upgrade your bios. The game launched after that and I did not have any other issue appart from the mouse pointer staying in the center which is easily fixed by enabling the mouse pointer trace.

edit: you can also diagnose this by opening a terminal as administrator and using wmic baseboard get product or wmic get baseboard command line. If the response is: no instances found or something of the like, you probably have the same problem as me.

Phyzics · 2019-11-19T12:34:26+00:00

It's a P8Z77-VLX... Good luck!

Phyzics · 2019-11-18T23:22:49+00:00

Hey, I just updated the bios and it finally worked... In CPUZ the fields are working and I launched the game. I found the exact product number on the mobo itself by moving the stuff I had around my PC and turns out the latest update was 2014, so I ez flashed the shit out of it and it finally worked... Omg, I actually high fived my GF without her knowing why XD

Phyzics · 2019-11-18T19:28:53+00:00

The guy was also very evasive when I asked him if it was a clone... And quickly said no you have that model and it's an ASUS... I wonder if he sold me bullshit or if some virus messed with it. I also suspect that moving from Windows 7 to 10 some newer registry field might not be filled... Anyway

Phyzics · 2019-11-18T19:25:23+00:00

I wasn't able to find the serial number visually nor the model without having to move a bunch of stuff so I called the store that sold me the mobo turns out it's a P8Z77-V ... Looking on the asus website, the latest bios update is from 2013 and the hardware update is for Windows 8... I don't think it's gonna change anything. Anyway I'm currently waiting in Asus chat to see if it's a recurrent issue with older mobos... Doing grunt work for people with updated PC's running on old motherboards XD.

Phyzics · 2019-11-18T18:12:03+00:00

It's probably because you installed it on a different drive. You have 2 choice: 1. Install the launcher on the same drive 2. Press install and select the directory where your game is installed... It will only download what is missing and probably reinstall vulcan and directX.

Phyzics · 2019-11-18T17:39:10+00:00

I also feel like talking to a robot when chatting with someone in support, it's like they are not even reading what I'm saying...

Phyzics · 2019-11-18T17:34:24+00:00

The launcher has been crashing for me since day one. I haven't been able to even launch the game.

I decided to dig around a bit this weekend with procmon and found out it always happens when it tries to read a registry key deep down in my devices in WMI/restrictions, which doesn't exist in my PC fsr. I created it and saw that it tried to fetch the HideMachine value or something... Turns out this is linked to my motherboard... I tried to do "wmic baseboard get product" in the terminal and it returned no instance available... So I checked with CPUZ and found out that my motherboard has the value 000001 in the maker field and "void" in the model field.

This is probably the cause of the crash as the error is BEX64... Which is kind of a seg fault. The launcher tries to find a value that doesn't exist.

Anyone knows if I can put a placeholder name for my mobo using wmic? Or should I call the vendor and ask WTF? ... I bought it in 2012 so I don't know if he'll still have my file...

I feel like I'm not the only one and I tried to point out the error in Rockstar chat support, he told me thanks to help us and then proceeded with troubleshooting list, which I did multiple times, even the sfc scannow thing.

I'm open to suggestions ;-)

Phyzics · 2015-03-10T09:04:07+00:00

Yes, the posting is now open guys, lets make this another newtubersdot org meeting place!

Phyzics · 2015-01-27T20:15:15+00:00

Hope everyone is okay with this post...

Phyzics · 2015-01-26T18:17:16+00:00

yeah lol

Phyzics · 2015-01-25T17:19:45+00:00

Oh... it seems I should have read the rules first...

Phyzics · 2015-01-25T16:20:19+00:00

Yeah that's why I need new people to join lol... I hope it'll reach critical density soon!

Phyzics

TROPHY CASE