Trying to find out which PNG formats are not loading / show messed up of me. (Proton Hotfix atm)
I could really use a IT expert on Window to re-test this on Windows.
I'm completly puzzled where that damn loading bug really is, because I'm very confident that I myself did use 1bit alpha textures...
Will be testing this for a while with a fresh empty cache folder.
So far is seems stable with Proton under Linux. Technically the same Windows-setup, except that for BepInEx I need an extra Steam launch parameter.
I have no doubts you used the base mesh properly since you mentioned it very clearly.
I completely retopologized it manually into a clean quad mesh and shrinkwrapped it.
The funny thing is you may be putting to much effort into it with this step. For typical much larger clothing items covering...
This will be a controversial thing for a long time.
*grabs popcorn* :unsure:
I can see why people critque it for destroying the artistic style. But at the same time it is an unofficial leak and obviously *intended* to be used for realistic style games.
So in my book poeple are judging it for it...
Doesn't VaM use smoothing for clothing already?
I know the following exists and I'm pretty sure this is computed inside a shader on the GPU too. Afaik there is just a lack of "control" over it.
It's a sort of "hidden" setting and not accessible via VaM's UI and defaults to a "smoothIterations"...
That would be a very exotic audio setup - I think the Unity Engine audio may already be the dealbreaker here to achieve this.
One would have to dig through the Unity 2018.1 audio documentation to figure out if it's possible to write a custom plugin for this audio setup.
However, I can at least...
Somebody would have to point a gun at me to force me back to use Windows again.
Meanwhile tested out other Distros - Had Bazzite on another drive temporary - very nice for a pure "I just want to game" setup - but not for me with the immutable kernel.
A few month ago I managed to set up VaM 1 as...
My new fav. download more RAM Linux magic trick after upgrading to AM5, but being unable to afford more than 16 GB DDR5:
sudo apt install zram-config
Did configure it to use stronger 'zstd' RAM compression algorithm and it's like having 24 GB RAM at least.
Microslop can f*ck off. Never...
I was able to reproduce a similar error.
Also triggered by System.Drawing.GDIPlus.CheckStatus, with the files in this VAR:
https://hub.virtamate.com/resources/pattern-textures.32186/
The "bad" PNGs:
pattern_melons_colored.png
pattern_ice_colored.png
pattern_pineapples_colored.png...
The errors shows a callstack of all function where a parameter is already invalid / 0, but it's unclear why.
Can only guess:
Proton compatibility layer is not really being 100% compatible with Windows GDI functions and that's why is fails with some of the System.Drawing function calls.
I think...
I really hope more people try Linux! Mint is perfect for beginners and it's free.
The basic steps to make VAM run are:
Install Linux Distro + GPU drivers if needed (Mint has a Driver Manager for that, no need for cryptic terminal) + Steam + Proton.
Add VAM as custom game to Steam and enable...
I think internally (VAM code) the way the user interface rendered was based on the resolutions height. Width was ignored.
Ultra wide Monitors work perfectly fine with an aspect ratio higher than 1.777.
Only old style 4/3 ratios or similar far below 1.777 caused that UI problem.
At least that's...
Only had time for a quick test: Yup, no more physics explosions. (y)
So now, by default, it disables the time sync if fps < physics rate if I understand correct.
And this safeguards against the "slow CPU cannot keep up"-scenario.
The issue is most likely from the aspect ratio of that resolution.
The user interface of VAM 1 was mostly build for 16 / 9 = 1.777 with some wiggle room.
1280 / 1024 = 1.25 is to far off.
A higher 1600 / 1280 = 1.25 resolution would have the same problem.
To fix that on a monitor with that...