I've had this issue happen in VR, but I assumed it was because of VR itself. If it does it, I just try restarting it again until it doesn't crash.
Are you clicking out of the program when it runs? What operating system are you using? Are you using the installer or the archive? Have you tried lowering the settings?
Hmm, that's worrysome. I haven't run into any crashes myself.
If you're running the zip version, can you please take a look in the yiffalicious_Data folder and locate output_log.txt (after crash)? Please paste the contents at http://pastebin.com/ and link it here.
I'm getting crashes with this new version as well. They're making my graphics driver crash or something. Both of my monitors go black and then after a couple of seconds, they start working again, and I get a message in my toolbar saying that my AMD display driver has restarted. It seems to happen after a few minutes regardless of what I'm doing. And this did not happen with version 0.5.4. My display drivers are up to date and I'm not using VR.
I'm running in 1600x900 windowed mode and my specs are:
Windows 7 64-bit Intel i5-2500 Radeon HD 6970 8GB RAM
EDIT: Yiffalicious just freezes, it itself does not close, but it is unresponsive after the display driver crashes. Also, output_log http://pastebin.com/J8MeUJDC And I am using the zip version.
Radeon cards in both cases. I'm starting to think it's isolated to those as I'm unable to reproduce this (I'm on GeForce). Either case, I need those log files. Please share them.
BallisticD said: Same here, also been getting display driver crashes on windows 10 with the installer.
Leaving Yiffalicious open, but not as the active window on the default level for ten minutes does not result in a crash. Opening the official dragoness3 interaction and leaving it running on the "First?" snapshot for 15 minutes, but not as the active window does not result in a crash either.
I can reproduce the crash 100% of the time (9/9 times) by loading the LoneDuck2 interaction that is on the first page of the interactions sorted by new and playing it, followed by zooming in all the way using my mouse wheel and zooming out so that the characters are both entirely in frame. Repeat zooming in and zooming out until the crash happens, it usually take two 'zoom in zoom out' loops.
I can tell you with 100% certainty, that it has something to do with tessellation, it runs perfect, and than crashes as soon as I enable tess. And it also seemed to run fine with the graphics set to lowest.
On "Fastest" with everything disabled in the graphics menu the crash does not occur, even if DX11 Tesselation is enabled. The same goes for "Fast." On "Simple," and "Good," the crashes where Yiffalicious freezes and the graphics drivers restart, occur when DX11 Tesselation is enabled. On "Beautiful" and "Fantastic" with DX11 Tesselation enabled, I get a much worse error, where (my guess is that) my graphics drivers do not restart and I have to perform a hard shut-down of my computer. I'm inclined to think that it has something to do with tessellation and AMD graphics cards. This is all on the LoneDuck2 pose, I'm not sure how to load the pose file that you linked, odes.
I think I have an old radeon lying around somewhere. Being able to test myself is far better than sending test builds back and forth. So I'm gonna try and find it. Right now I'm fixing some other bugs tho. But I'll probably start looking at this tomorrow.
r9 290x here driver hangs sometimes not always. Last time it was 3 times when i tried to move the camera then it worked. Also please be aware that due to the driver reset, the video card cooler wont reset to idle / low speed afterwards until you restart your pc, which isnt a good thing for the gpu, just a warning. Also no log is generated because the game doesn't crash, it just gets stuck/freezes/black-screen.
Ok, so some progress guys. I've managed to reproduce this error on a radeon rig I built, and in a very small isolated project using standard assets. I've uploaded this project to unity in a bug report. Not sure what more I can do. For now tessellation will just default to off on non-geforce hardware in the upcoming patch.
Getting the same issue with an AMD R9 290X. All settings, including Tesselation, are off, except for Multithreading and the Driver Quality (which is set to max because, well, shoulders).
Friend says it may have to do with Direct X? Dunno.
Problem is, it isn't a tesselation issue, it happened even when it was disabled. On the other hand, after disabling multithreading the issue only happened once. Not sure what is causing it, it seems to be rather random, there are things that decrease the chances of it happening though.
For me, the entire game freezes for a few seconds and then I get the notification that the display driver stopped working and recovered. The game stays frozen, however, and you have to Ctrl+Alt+Del out of it and restart. I'll screw with it a bit and see if I can iron out what it is.
Comments
Radeon R9 390X
AMD FX-8320
16GB RAM
It just crashes sometime after starting up.
Are you clicking out of the program when it runs?
What operating system are you using?
Are you using the installer or the archive?
Have you tried lowering the settings?
Otherwise, I think it's just a bug with the game.
If you're running the zip version, can you please take a look in the yiffalicious_Data folder and locate output_log.txt (after crash)? Please paste the contents at http://pastebin.com/ and link it here.
I'm running in 1600x900 windowed mode and my specs are:
Windows 7 64-bit
Intel i5-2500
Radeon HD 6970
8GB RAM
EDIT: Yiffalicious just freezes, it itself does not close, but it is unresponsive after the display driver crashes. Also, output_log http://pastebin.com/J8MeUJDC And I am using the zip version.
And I'm running Windows 10, and am using the installer version.
I have two using crossfire but I don't think Unity utilizes that even in fullscreen mode iirc.
Things to try:
* Does this happen in other levels?
* Does this happen even when there are no characters present?
EDIT: just in the background.
@SexyLizard69 does that cause a crash for you too?
Basically using this pose file, and zooming in and out. (I can't reproduce it on my system though.)
https://drive.google.com/open?id=0B03O3-piMMqQWlNKczl3Q0tXUDg
%appdata%/yiffalicious/interactions/local
Friend says it may have to do with Direct X? Dunno.