Wrong quote , dude.Look at this thread. It's everything you need to know. You will also find the direct download link to the UABEA tool
Wrong quote , dude.Look at this thread. It's everything you need to know. You will also find the direct download link to the UABEA tool
That would be a shame if they did that.........What tool are you using? I've tried AssetStudioModGUI and UABEAvalonia and I can't find any mosaic material; only gameobjects and monobehaviors. If I look in sharedassets0.assets I can see two mosaic materials called Mosaic 64 and Mosaic 65. When I went to the shader they referenced and edited all colmask values to 0 or 1, the game just crashed on start.
I can try to upload the game somewhere so you can see what I am talking about. Perhaps they changed the mosaic on one of the updates...
are you sure you can not find the mosaic in ressource.assets anymore? If so then yes, they probably changed itWhat tool are you using? I've tried AssetStudioModGUI and UABEAvalonia and I can't find any mosaic material; only gameobjects and monobehaviors. If I look in sharedassets0.assets I can see two mosaic materials called Mosaic 64 and Mosaic 65. When I went to the shader they referenced and edited all colmask values to 0 or 1, the game just crashed on start.
I can try to upload the game somewhere so you can see what I am talking about. Perhaps they changed the mosaic on one of the updates...
Maybe try original UABEA, not "NEXT".I am using thisYou must be registered to see the linksbecause nothing else seems to find the mosaic material. But, the problem is that editing the shader crashes the game and I have no idea why.
I did but I can't find the mosaic materials with that version.Maybe try original UABEA, not "NEXT".
However, it's strange. It's sounds like there's some kind of "protection".
Everything is correct..That's how it was in the older version.This is what I'm working with right now.
View attachment 5403018
View attachment 5403019
If I change anything and I do mean anything in this shader, it crashes the game.I wonder if the security update for unity had to do with some malicious code execution from a shader...Time to do some digging. Never mind, the vulnerability did not have anything to do with shaders.
game was updated to v1.1.0. edit a sharedassets0.assets again. I have no problem. ID is 2951 ?Everything is correct..That's how it was in the older version.
Strange that a modified mosaic shader could kill the whole game now.
kumarin More problems...
Checking now.game was updated to v1.1.0. edit a sharedassets0.assets again. I have no problem. ID is 2951 ?
I guess it doesn't really make a difference whether you edit directly or "dump".I tried editing the shader within the program and also by exporting the shader and editing with Notepad++ then importing and they both crashed the game.
Maybe. . I use the original UABEA, not "NEXT ". It's more stable version.Well it worked... Maybe it was the tool? Were you using UABEA Next or no?
I can't open the game with melonloader. It gives the error "Class::Init signatures have been exhausted, using a substitute!" I'm using version 1.1.0. Did you get the same error?I couldnt find any working bepinex for this game cause it's unity ilcpp and I think this game is on the latest version of unity..
Even tried it to get working with Melon Loader but it is not translating everything.
You can get the game at Ryuugames:You must be registered to see the links
I got the same error but the game did not crash when I was testing it. The translation only worked in the dialogue but not on the buttons and it was a little bit delayed. I haven't tried it on the new version though.I can't open the game with melonloader. It gives the error "Class::Init signatures have been exhausted, using a substitute!" I'm using version 1.1.0. Did you get the same error?
Had the same error and also crash, updated to nightly build melonloader and after like 2 tries it suddenly started running, you can maybe it will somehow magically work this way for you too lolI can't open the game with melonloader. It gives the error "Class::Init signatures have been exhausted, using a substitute!" I'm using version 1.1.0. Did you get the same error?