Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

AppGameKit Studio Chat / [SOLVED] Something went wrong with last Classic and Studio updates?

Author
Message
psychoanima
1
Years of Service
User Offline
Joined: 19th Jun 2018
Location:
Posted: 12th Aug 2019 21:28
I suddenly start experiencing problems with my shaders on both versions, since last update.

When I run my game in classic AppGameKit I am getting these errors:






and in Studio version these two:








I have to mention that when I broadcast my game on a cellphone device everything is working normal.



Attachments

Login to view attachments

The author of this post has marked a post as an answer.

Go to answer

psychoanima
1
Years of Service
User Offline
Joined: 19th Jun 2018
Location:
Posted: 12th Aug 2019 21:31
pixel shader





vertex shader

psychoanima
1
Years of Service
User Offline
Joined: 19th Jun 2018
Location:
Posted: 15th Aug 2019 20:00
Anyone?
Cliff Mellangard 3DEGS
Developer
13
Years of Service
User Offline
Joined: 20th Feb 2006
Location: Sweden
Posted: 15th Aug 2019 20:04
SFSW
17
Years of Service
User Offline
Joined: 9th Oct 2002
Location:
Posted: 15th Aug 2019 21:32
The solution is in the error messages it is showing you (different types across shaders). I'd recommend this thread for one/another route of shaders issues: https://forum.thegamecreators.com/thread/224812

In short, and you may already be aware of this first one, there are currently some sequential requirements for shader values (varyings) that need to match exactly in order within both the vertex and pixel/fragment shaders you are using. Also, the new compiler will display an error if you try to blend types using the same label across both shaders. So those are the primary things I would recommend checking into and changing things as may be needed.

At a quick initial glance, it appears you are trying to use two different array quantities under the same label across both shaders: agk_bonequats1[28] vs agk_bonequats1[100] and agk_bonequats2[28] vs agk_bonequats2[100] So you might want to try changing the value labels in the pixel shader, aligning the indexes, and/or transferring the original value(s) over to a different label in the fragment shader as may be needed.
Paul Johnston
TGC Developer
17
Years of Service
User Offline
Joined: 16th Nov 2002
Location: United Kingdom
Posted: 29th Aug 2019 14:19
This post has been marked by the post author as the answer.
SFSW is correct that the different definitions of agk_bonequats1 is the cause. However agk_bonequats1 and agk_bonequats2 shouldn't be defined in the pixel shader since they are never used there, removing them from the pixel shader would also fix the error.
psychoanima
1
Years of Service
User Offline
Joined: 19th Jun 2018
Location:
Posted: 29th Aug 2019 23:00
thanks SFSW and Paul,

removing agk_bonequats solved my issue. Interesting how recent version of AppGameKit actually ignored this problem.

Login to post a reply

Server time is: 2019-11-21 11:00:12
Your offset time is: 2019-11-21 11:00:12