El Bromas (2019)
Newbie
- Jun 10, 2017
- 69
- 58
- 198
Very strange, happens the same thing with me, I played the 0.39 version normally and now tried to play 0.40 and the game just crashes
El Bromas (2019)
Newbie
- Jun 10, 2017
- 69
- 58
- 198
Tried that, updating drivers, installing and reinstalling the visual studio redist, and no change. I should say that v0.39 works fine. Here's my specs as far as I remember:
Processor:Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz 4.00 GHz
RAM: 16 GB
GraphicsCard:NVIDIA GeForce GTX 780
Running Windows 10
Hmm,
It's working for me.
after install Microsoft.HEVCVideoExtension.Appx packed inside the game folder.
But, the application runs for native resolution only which means for me 4K.
So, it runs slowly for me.
I need to change the game's resolution down to 1080p for make it runs smoothly, but there seems no option for change it in the game.
ps. I changed my monitors resolution to 1080p, and get 27fps now.
This seems heavier than last version.
I could get 58fps last version with 8750H and gtx 2070 laptop ver.
It's working for me.
after install Microsoft.HEVCVideoExtension.Appx packed inside the game folder.
But, the application runs for native resolution only which means for me 4K.
So, it runs slowly for me.
I need to change the game's resolution down to 1080p for make it runs smoothly, but there seems no option for change it in the game.
ps. I changed my monitors resolution to 1080p, and get 27fps now.
This seems heavier than last version.
I could get 58fps last version with 8750H and gtx 2070 laptop ver.
Last edited:
even after th installation of Microsoft.HEVCVideoExtension.Appx it still crashes at start
Main performance impact appears to be mesh baking for physics. This is done so often that it causes spikes.
Many systems are bound by this: character collisions, fluid particles, you get the idea.
It's not really possible to switch this off, perhaps instead a fix might be subbing it out for a more performant solution. Unfortunately this would itself require a rewrite of all of the physics so it's not likely.
As a result it's safe to say that the performance cannot be fixed.
Some basic Unity profiler data
Game is designed to target 60fps, struggles to hit 30 when idling.
Alternative solutions might be staggering mesh baking or else providing proxy meshes for collision.
Many systems are bound by this: character collisions, fluid particles, you get the idea.
It's not really possible to switch this off, perhaps instead a fix might be subbing it out for a more performant solution. Unfortunately this would itself require a rewrite of all of the physics so it's not likely.
As a result it's safe to say that the performance cannot be fixed.
Some basic Unity profiler data
Game is designed to target 60fps, struggles to hit 30 when idling.
Alternative solutions might be staggering mesh baking or else providing proxy meshes for collision.
Prick
Engaged Member
- Jul 17, 2017
- 2,312
- 2,200
- 477
Those of you who are crashing, find the log file and share what access violation is present.
Appdata\LocalLow\HenryTaiwan\TrueFacials\Player.log
Someone from discord said their log is "libvhacd.dll caused an Access Violation (0xc0000005)"
But it could be different for other people.
From a little bit of quick research on the .dll, and the access violation it could be a number of different things.
We can rule out that all of you have could have a bad ram stick, or corrupted Windows, or bad HDD / SSD.
Most likely the issue is something within Henry's code which is present with this beta build.
But it could also be an obscure software package that some of us happen to have installed.
I'm also wondering if anyone is crashing with an RTX equivalent / greater graphics card.
I've got a 2080, it's chugging but it runs the game without any crashes or weird behavior.
Also, the log file shows that this game is dependent on DirectX 11.1.
You can check what version of DirectX your system supports by pressing the Windows key + R on your keyboard, and type "dxdiag" in the box.
If you don't have DX11.1, (or DX12) that would definitely explain the crashes.
Appdata\LocalLow\HenryTaiwan\TrueFacials\Player.log
Someone from discord said their log is "libvhacd.dll caused an Access Violation (0xc0000005)"
But it could be different for other people.
From a little bit of quick research on the .dll, and the access violation it could be a number of different things.
We can rule out that all of you have could have a bad ram stick, or corrupted Windows, or bad HDD / SSD.
Most likely the issue is something within Henry's code which is present with this beta build.
But it could also be an obscure software package that some of us happen to have installed.
I'm also wondering if anyone is crashing with an RTX equivalent / greater graphics card.
I've got a 2080, it's chugging but it runs the game without any crashes or weird behavior.
Also, the log file shows that this game is dependent on DirectX 11.1.
You can check what version of DirectX your system supports by pressing the Windows key + R on your keyboard, and type "dxdiag" in the box.
If you don't have DX11.1, (or DX12) that would definitely explain the crashes.
I can start the game. But i get a grey screen. I can press ctrl. And see commands and etc. And i can see the right menu. But else, it is grey.