I need you help in identifying the bug.
Added 2025-10-09 10:32:53 +0000 UTCComments
In v2.1.5, pressing F5 opens the menu in Maker, but it does not work in Studio. Pressing F1 allows you to check the version itself, which displays as 2.1.5.
リーベルト ヨハン
2025-11-13 04:02:30 +0000 UTCI've had this problem for several versions, but it seems random and doesn't happen very often. I restart studio and it goes away. I can't provide exact details, because I don't know why it happens. I can only guess. I think it occurs more often when I'm re-editing older scenes. Perhaps if a scene was initially created with GraphicsMod 0.5.2 there may be left over data in the scene causing issues? When it does occur, it seems that toggling AA modes, SEGI, and certain post-processing settings can cause it to "flicker" and temporarily fix itself. I don't know what this means. It doesn't happen often in the current version. I've only had it happen once in a particular scene. I ended up setting the graphics settings to studio defaults and redoing them, and haven't had a problem since.
Blackrain
2025-11-09 01:55:05 +0000 UTCI'm also having this same issue, after a short amount of time the character and ui goes black. I've tried using FSR3 to no avail... EDIT: Once I turned off AA I no longer have this issue it seems.
BakunyuuWaifu
2025-10-28 21:23:46 +0000 UTCI have another issue that I find the video export plugin couldn't work well with your new screenshot engine. You know the video export plugin can invoke screenshot manager plugin to capture a sequence of pictures. I set resolution to 4k/2k but video export output only the bottom left corner of the image, with resolution 1k to be the full. I'm sure my plugin is the newest version, and I don't know if I have the wrong settings. My red output-log is "Dimensions of color surface does not match dimensions of depth surface". Can you tell me weather it's a bug or how to adjust the settings?
Taomadehanzi
2025-10-26 15:31:53 +0000 UTC2.15 does not support VR?
Taja Guo
2025-10-21 14:19:49 +0000 UTCmy bepinex log does not show any errors, before it starts it's doomscroll when HS2 glitches.
Craig Monroe
2025-10-19 21:30:42 +0000 UTCThe error with the black UI and blacked out skin appears for me both in Studio and in Chara Editor, and was an issue before version 2.1.5. I’m sorry, but I don’t remember the exact version update it first appeared for me, but it did appear coincident with one of your updates. I don’t usually use CTAA, so it appears even when not using CTAA. It usually manifests if I am working in Studio or Chara Editor for a long period of time, but seems to appear sooner if I have both open. I will try to remember to send you the output log the next time it happens.
yakfur
2025-10-12 02:09:56 +0000 UTCI am encountering this after leaving both Chara Editor or Studio "idle", running in the background without activity for several minutes. By default I am running CTAA standard. It doesn't happen when I am actively working even for hours. This behavior I had way before 2.1.5.
Archimalaka
2025-10-10 19:48:30 +0000 UTCI have been encountering this for a bit, like others have said after some time the characters lighting will seem to "break" and flicker and screen shots are a solid black. This usually occurs in the character creator, but it has been happening in the studio environment as well I have found one error in the recent update when using the studio items such as the smartphones that simulate having the camera on. Looks like it is linked to the Screen Space SSS. When it's enabled it duplicates and creates a ghosted/distorted version of the character along side the blackened character and with Screen Space SSS disabled it no longer duplicates the character, but they are entirely black. Just launched the studio to check some of my settings and had it open with no scene loaded and CTAA was the default AA option and after some time the black flickering began, checking the output log I see "[Debug : Graphics] CTAA updated. Supersample Mode: STANDARD => STANDARD Source Size: 3440x1440" being repeated over and over for some time. I also just tried a fresh launch of the studio and put the AA to FSR3 (quality option) right away with no scene loaded and left it for 15-30 min and no flickering was occuring.
Mr Pletz
2025-10-10 13:48:13 +0000 UTCIn this version of Graphics Mod, I haven’t had those problems. Maybe I’m just lucky, or maybe it’s because the first thing I do is load my general preset. When a new version of Graphics Mod comes out, I update my presets to use the new features. So I use Amplify, Beautify, FSR3, etc. instead of GTAO or CTAA. And it seems that by doing this, I avoid a lot of issues. I know this isn’t the solution, but one way to minimize problems is for Hanmen to update their presets to use the more modern features—especially the Maker and Studio presets—so they use FSR3 and Amplify. I suppose that might cause some issues for certain people. But I still assume that almost none of us use the default presets to render a final image. In Maker, I use the default preset to save a card and make the character have as few lighting, illumination, skybox, and post-processing effects as possible. I leave that part to Studio. And in Studio, I only use the default preset to do light testing before overloading my computer with more powerful stuff. If Hanmen thinks he should spend weeks or even a month fixing bugs and making everything run better before adding new content, he should feel free to do so. From version 1.9 until now, the new features have been very good—but also very disruptive. And while I’m thrilled, it’s normal for new technologies to cause problems when integrating them with older ones. Personally, I prefer adding new things on a solid foundation rather than continuing to carry old problems from the past. Edit to add: I’m an old Studio user, so I’m used to its performance issues. Every 30–60 minutes, I close Studio and reopen it. And I know that saves me a lot of trouble, like the ones mentioned in this thread.
pemoj
2025-10-10 08:36:18 +0000 UTCI’ve actually had this bug for quite a while, since the 1.x versions. From my experience, CTAA seems to trigger it much faster than SMAA. Back in the day when I used the ACES preset with SMAA, it still happened occasionally, iirc. Also, I’ve noticed it occurs more often when the scene is mostly empty, but for scenes with crazy graphic settings or lots of detail (SEGI + lots of light sources), it’s actually less likely to happen
Hyperion06
2025-10-10 04:19:45 +0000 UTCBeen having this issue since BetterRepack R4. Whenever I leave Studio or chara creator open for too long, UI breaks and rendered screenshots become dark. Was still having it with GM 1.9.5. It stopped when I started using my 4k TV as a monitor. Studio and char creator have been open for 13 hours straight today and nothing happened. Could be just a coincidence.
Rochin
2025-10-10 04:17:16 +0000 UTCThe black texture thing has happened to me multiple times when I accidently leave studio running when i have to stop and do other things or tab out watching something. Generally takes awhile. Happened way before this update and happens only on certain maps oddly, not all. Also the ammount of time passed before it happens tends to vary. Usually way over an hour or more. I Haven't had any UI issues however (aside from one that occasionally happens unrelated to this, i'll assume). Next time it does, I'll send log.
Cobra Kumanda
2025-10-09 22:26:50 +0000 UTCI have the same issue. I use CTAA almost exclusively, but even when i don't the game will still break. It usually happens when I have been in studio or character creator for 20 to 30 minutes. The studio can't find any scenes or characters I have saved. If I go to look up studio props or maps, most of them are not listed either. The only solution I have found is exiting the program and starting over. Which gets really annoying having to do that every half hour.
Craig Monroe
2025-10-09 22:03:56 +0000 UTCSome short if map having ait with emission shader could be black mass dot nearly boundary of shadow "agx" If using HDR ACES not seam to appear
Emma Amelia
2025-10-09 16:23:07 +0000 UTCDo you have spam errors in the console?
Hanmen
2025-10-09 14:45:57 +0000 UTCI have this issue as well. It tends to just sort of happen if I leave the game open and just alt tab a whole bunch. I just save the scene and relaunch. I also should note I don't play with the game staying open when I alt tab or studio isn't the focused program or window, but I do have the program full screened and not windowed or borderless windowed.
Legato
2025-10-09 14:36:33 +0000 UTCThe UI issue sometimes occurs at startup. However, the black textures occasionally appear after leaving the studio running in the background for a long time. Sometimes, they also show up when adjusting lighting and shadows. Apart from a complete black screen, there are cases where the shadows keep flickering. That seems to be caused by a problem with the shadow rendering. Once, I tried turning the shadows off and then back on — the character became illuminated again, but the shadows were still problematic. The strangest thing is that I haven’t encountered these issues in the past couple of days, even though they used to happen frequently before. If it happens again, I’ll pay attention to its relation to the anti-aliasing settings and check the output-log.
tonydvd
2025-10-09 14:09:32 +0000 UTCEverything gets dark, eventually start flickering. Always happen with CTAA, but usually after hours of use. Never happened with SMAA.
Henvoxy
2025-10-09 14:07:51 +0000 UTCYup. I had CTAA spam the console a lot so I though that was the issue, but still happened with it off. The other only things enabled were bloom and GTAO, and the pulse probes. I think it's the ambient occlusion yes, or any of the other post FX that are constantly updating.
Ruykiru
2025-10-09 13:54:15 +0000 UTCNot sure about the UI or the GM version, but this is like the thing from GTAO since the old Graphics Mod. Having the studio idle for too long, the textures break, the scene darkens, and saves are gone. The only way to resolve this is to restart the studio. A temporary fix when this happens is to switch to a different AO, just so you can save your scene before restarting the studio. The same thing still happens in your version of GM. May that be in the studio or the chara editor. Leave the scene on idle for like... 15-20 mins while on GTAO, and the scene just breaks.
NiiChan
2025-10-09 12:20:11 +0000 UTCit happened for me when using CTAA standard cant say about the other CTAAs
ol'geezer
2025-10-09 11:58:33 +0000 UTCI'm not sure if it's the same bug manifesting in a different way. But I have had a texture bug when I was experimenting with the new FSR, where all textures were low resolution when using anything other than FSR. If I remember correctly it was when I had FSR enabled but then loaded a preset that had TAA enabled instead. Like the game was still running lower res, but without the upscaling of FSR. Edit: I had to reload studio in order to fix it. Also noticed the sharpen post process effect gets broken with FSR and has to be reenabled when switching back to another anti-aliasing method.
Saul Goodman
2025-10-09 11:07:30 +0000 UTCthe game generally got broken not only UI, but overall all textures broken or dissapeared and nothing helps until you restart the game
Hanmen
2025-10-09 10:46:10 +0000 UTCIf it's about UI disappeared, for me, the easy fix was just to press the escape button until the "do you want to quit?" Message appeared. Somehow, pressing no will fix fhe problem.
MikeC
2025-10-09 10:38:16 +0000 UTC
