... looks like you can still at least see the scenes by going into appdata/locallow/blueribbon etc/temp, while the game is running.
It's a pity, because from playing 0.3 I can tell that this is a really unique type of game and it appeals to me a lot in terms of presentation, fetish stuff and how all of that interacts with the gameplay. ...
Oh, I'd assumed they were encrypted or something even in the temp folder.
Also yeah, I hear you, here's hoping...
So far i look on the Unity side i know it isn't a CPU Problem its a Codec Problem.
There some Codec Problems With H.264 mp4 Codec from AVPRO.
I have H.264 and H.265 on my machine and in VLC they run when i convert Videos without any problems.
On Win 7 Systems that AVPRO make massive Problems i don't know maybe he use a buged AVPRO Version.
That Problem was on the 2019 Unity maybe in 2020 Version too that he use in the Project.
I feel like I have those codecs, but there's a chance that I don't (or maybe ones I have are an issue), I'll see what I can find...
(Maybe I can just check the temp files to confirm...)
Cheers for looking into this and sharing your findings.
If you want to help so much, you can talk at my discord but the problem is very rare and don't have much to do.
If I were you and I got something to help, I would just go to discord server, bug channel and explain it to me. But as you can't talk like that there, your real purpose is not helping but just this..
Firstly, posts in discord servers are not visible via search engines (to my knowledge), so posting in public forums allows anyone to find this info, particularly end-users (also I was replying to a forum post in said forum). I'm not anti-discord or anything though, I just feel like troubleshooting some things publicly has benefits.
Secondly, from what I was able to dig up earlier, is that you've been aware of this particular issue for (at least) 3 months, so asking you for assistance, publicly or not, would be an insult, as if to imply, what, that you might have a solution that you are not doing anything with? Instead, I chose to ask if what you said in a particular forum post is true, and for any additional details, while sharing my findings.
Plus, I felt that since the issue didn't have much of any diagnostic information here, that talking about it might drum up a more thorough look by other members. With the number of Unity projects around here (and in general), there's plenty of users with the know-how that I lack to see more than I can.
As far as purpose goes, I had two in particular. As I'd alluded to (or maybe more explicitly suggested), the post initially started as a query about the issue with regards to CPU compatibility, as I'm set to replacing that part of my machine in the future, and after doing searches into the problem and seeing that what you'd said and what I'd found didn't line up (bordering conflicting information), I additionally questioned your information and it's source (which I assume to be coder)...
Just calling my coder bad, would not help anyone.
I never called your coder bad nor would I consider it without at minimum digging through the code personally. That said, I'm not a programmer, just a dabbler, so I have little to no experience nor authority on subjects of coder/coding quality anyway. Maybe that's all besides the point though...
I shared my suspicions which were formed from digging for information on the bug I (and others) have encountered, and in doing so I cast my suspicions on coder-san (I don't know their name), but not you. As for why, I simply believe, no question, that you'd fix the problem if you knew how, where a coder... ... ... may not... either by being unable to (skill, hardware/software incompatibility, etc) or by choice (lazy, other code/work priority, etc)...
All the same, that's all they are, my suspicions, if I'm wrong, I'm wrong, do with them as you will.