darta Posted August 24, 2023 Posted August 24, 2023 On 6/28/2022 at 12:50 PM, 911reg said: try this one instead, i cleaned it off a bit so it's really lite, just make sure to put it in your client's root folder, otherwise some texture dependencies might get fucked up. Plus you can directly open the client's utx files without having to decrypt them https://drive.google.com/file/d/1jTiNqL6R-Bq5ISJUNG-sMIzcO5YN_5d2/view?usp=sharing yours still give the rgbawsplit error in loggs.
911reg Posted August 24, 2023 Posted August 24, 2023 4 hours ago, darta said: yours still give the rgbawsplit error in loggs. wdym? which logs?
darta Posted August 26, 2023 Posted August 26, 2023 (edited) On 8/24/2023 at 8:14 PM, 911reg said: wdym? which logs? in l2.log of the game, using your client the icons i make still generate the rgba error, but his not, could you fix? Your editor processes total animation time good, but his does not , generates a huge number whatever you write (if total frame number u insert 16, 23, anything, it shows after as 1453832) Edited August 26, 2023 by darta
911reg Posted August 26, 2023 Posted August 26, 2023 (edited) 12 hours ago, darta said: in l2.log of the game, using your client the icons i make still generate the rgba error, but his not, could you fix? Your editor processes total animation time good, but his does not , generates a huge number whatever you write (if total frame number u insert 16, 23, anything, it shows after as 1453832) forgot about that, at some point they added another int named RGBA8RawData to the Texture class, so when you save any texture it'll also contain that variable, tho since it doesnt exist in older clients it'll just throw a warning. This can be ignored mostly but it annoys the fuck out of me, gonna upload a fix to my topic in a bit, but basically you can simply go to Object > Material > RenderedMaterial > Texture, scroll down to the bottom and delete the .int, then recompile changed scripts, and save the engine.u edit: @darta here you go Edited August 26, 2023 by 911reg 1
darta Posted August 28, 2023 Posted August 28, 2023 (edited) On 8/26/2023 at 9:02 PM, 911reg said: forgot about that, at some point they added another int named RGBA8RawData to the Texture class, so when you save any texture it'll also contain that variable, tho since it doesnt exist in older clients it'll just throw a warning. This can be ignored mostly but it annoys the fuck out of me, gonna upload a fix to my topic in a bit, but basically you can simply go to Object > Material > RenderedMaterial > Texture, scroll down to the bottom and delete the .int, then recompile changed scripts, and save the engine.u edit: @darta here you go would be awesome if you could fix and re-upload , tbh, Thank you so much . would be awesome if you could fix and re-upload , tbh, Thank you so much . Edited August 28, 2023 by darta
911reg Posted September 15, 2023 Posted September 15, 2023 (edited) 9 hours ago, darta said: i guess you will not fix this didn't my version work for you? i tested it and it seemed to work perfectly fine, no RGBA8RawData errors whatsoever Edited September 15, 2023 by 911reg
darta Posted September 25, 2023 Posted September 25, 2023 On 8/26/2023 at 9:02 PM, 911reg said: forgot about that, at some point they added another int named RGBA8RawData to the Texture class, so when you save any texture it'll also contain that variable, tho since it doesnt exist in older clients it'll just throw a warning. This can be ignored mostly but it annoys the fuck out of me, gonna upload a fix to my topic in a bit, but basically you can simply go to Object > Material > RenderedMaterial > Texture, scroll down to the bottom and delete the .int, then recompile changed scripts, and save the engine.u edit: @darta here you go i mean this, you said you will going to upload a version which has this fixed. I am not good at compiling.
911reg Posted September 25, 2023 Posted September 25, 2023 39 minutes ago, darta said: i mean this, you said you will going to upload a version which has this fixed. I am not good at compiling. I updated it as soon as I posted my comment though 1
darta Posted October 1, 2023 Posted October 1, 2023 On 9/25/2023 at 9:00 PM, 911reg said: I updated it as soon as I posted my comment though omg, i am terribly sorry, THANK YOU SO MUCH! i will test it now. don`t know how i missed it, i checked your topic daily weeks ago for a change. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now