Unsure, you’ll have to try and troubleshoot it yourself with all the information currently available, I’m not a wizard.
it says failed to fetch information
I have no idea what Vulkan Rendering or zavatarteam2 is.
I’ve only got my mouse and keyboard plugged in, I don’t have BitDefender, I don’t have any Logitech Products, i’ve already quit processes and Applications on startup.
I got crash when connecting a rumble activated [Installed Driver] gamepad controller (SpeedLink SL-6635)
0.601.0.6010507_20231105T105738Z_Player_E2D03_last.log (15.8 KB)
This is only client side (not studio)
Studio using this gamepad controller fine but no rumble feature (Rumble feature driver already installed)
Vulkan runs far better with studio than D3D11 ever has. Seems like a stupid arbitrary block to disallow use of vulkan on the client, and I would love to know the admin’s reasoning.
Is it because Vulkan on Roblox was made for mobile devices first?
My guess is:
More work for the Hyperion Development Team
They’re focusing on D3D to prevent any sort of hacking
It’s time consuming enough to focus on preventing one renderer from any ESP vulnerabilities let alone two
Hyperion shouldn’t be active in Studio, so Vulkan should work compared to the Game Client
Yes, this is exactly why. It is not an “arbitrary block” like some people would like to think. Their general expectation is that only Direct3D will be used on Windows, Metal for Apple devices, OpenGL for anything that’s old enough, which leaves Vulkan to be expected to only run on Android.
Vulkan is not blocked at all, it just has a poor implementation that causes issues with Hyperion.
No, not at all, that’s now how that works.
2023-11-05T21:07:14.634Z,280.634857,12e8,6 [FLog::Output] Flamingo
2023-11-05T21:07:14.634Z,280.634857,12e8,6 [FLog::Output] addedFlamingo
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] Fish
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] addedFish
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] Goggles
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] FlipFlop
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] BloxyCola
2023-11-05T21:08:35.421Z,361.421814,1d0c,6 [FLog::Output] Settings Date header was Sun, 05 Nov 2023 21:08:35 GMT
2023-11-05T21:08:35.422Z,361.422791,1d0c,6 [FLog::Output] Settings Date timestamp is 1699218515
2023-11-05T21:09:06.381Z,392.381104,1188,6 [FLog::Graphics] D3D11 FATAL ERROR: Device removed with reason 0x887a0006 (DXGI_ERROR_DEVICE_HUNG: La GPU no responderá a más comandos, probablemente porque la aplicación que realiza la llamada ha pasado un comando no válido.)
2023-11-05T21:09:07.572Z,393.572266,33c0,6 [FLog::Output] StartProcessException...
2023-11-05T21:09:10.829Z,396.829071,33c0,6 [FLog::Output] Studio D3D9 GPU: Intel(R) Iris(R) Plus Graphics
2023-11-05T21:09:10.829Z,396.829071,33c0,6 [FLog::Output] Studio D3D9 GPU: Vendor 8086 Device 8a52
2023-11-05T21:09:10.829Z,396.829071,33c0,6 [FLog::Output] Studio D3D9 Driver: igdumdim64.dll 30.0.101.2079
2023-11-05T21:09:10.830Z,396.830048,33c0,6 [FLog::Output] ESGamePerfMonitor GPU: Vendor 00008086 Device 00008a52
2023-11-05T21:09:10.830Z,396.830048,33c0,6 [FLog::Output] ESGamePerfMonitor GPU: SubSys 85f3103c Revision 00000007
2023-11-05T21:09:10.830Z,396.830048,33c0,6 [FLog::Output] ESGamePerfMonitor GPU: DedicatedVidMem 134217728 DedicatedSysMem 0 SharedSystemMemory 8475533312
2023-11-05T21:09:12.094Z,398.094086,33c0,6 [FLog::Output] Uploading crash analytics...
Now i get this after crashing… i finally got it to show the actual issue in the FloG file, can someone tell me what does this even mean?
Completely ignore this now, Roblox has decided to axe and brutally murder any and all non-production deployment channels. Including zavatarteam2
which helped some people fix crashing issues.
Now I can no longer archive the cool little easter eggs that don’t make it to prod by Roblox engineers
Apparently from what I’ve heard, majority of the crashing issues (same on Linux) has been resolved, let’s just hope something like this never happens again.
The GPU will not respond to further commands, probably because the calling application has passed an invalid command.)
Check if your drivers are up-to-date, that’s all I can say. (This error message from DirectX, not exclusive to Roblox)
This has been happening to me alot recently.
For some reason, sometimes it stops happening, then it suddenly happens again.
To me, this seems like a network-related issue, does the game crash at all? It just seems like Roblox is failing to load correctly causing the game not to initalise right.
i dont think sooo.
it does crash, the pictures were taken when the game crashed.
dunno how the hell the client messes up that bad the game looks like that.
No
OpenGL and Vulkan worked fine without crashing up until a few weeks ago.
D3D is the main focus at ROBLOX, any exploit prevention pipeline goes through this as they don’t want to add more work on top of what already needs to be done, it’s a waste of time to work on Vulkan and OpenGL when less than 2% of the user-base uses it, especially when it’s activated by FFlags
Also read the posts made by Staff before responding next time
Hello all, Currently, there are three known issues: Enabling the Vulkan renderer through local FFlags triggers Hyperion. An older version (2007) of xinput1_3.dll is incompatible with Hyperion. Bitdefender is incompatible with Hyperion. Fixes for the Bitdefender issue are in the pipeline.
OpenGL and Vulkan worked fine without crashing up until a few weeks ago.
Also read the posts made by Staff before responding next time
Trigger ≠ Block
Vulkan’s implementation is screwed up in Roblox, which causes Hyperion to believe something malicious is going on, fixes are on the way.
Has a fix been pushed out to the stable build yet?
On Linux, yes.
But for Windows, unsure, nobody has really been active in this thread leading me to believe that the majority of the issues that people described here was resolved but the issues varied to person to person.
The last LIVE deployment push was 12 hours ago (8th of November, 21:31 GMT)
I still experience random crashing after playing for a little while, no error log or anything, just like everyone else