I'm kinda disappointed with all this and sincerely see no escape. Shall i have to leave the android target due to S***fullness just like i left webGL for the same reason ? Making target transparent is the ( really amazing ) role of unity and thanks to gogol it's simply fu*ked-up.
There are many ( too many ) possibilities:Īll are unit圓D solutions requesting big bunch of code and time and at the moment i don't know wether or not this will mess-up my unity project or targets ( textures are not the same when you target android or windows ! ) So untill U3D dev team will offer us a tickbox on the build settings window, saying "create loader and scene so that gogol is happy" we are screwed The thing is that in unity we got no mean of creating this file ( i guess it can contain textures, assets, meshes, sounds, etc. The interresting thing from google ( interresting is not the right word. OBB solution is not one as gogol states it's now almost obsolete.īut as they're small-d1cked they only allow a 150MB loader and the rest ( real usefull data from our unity projects ) in another file. unity 150MB warning is useless sh1t ( and bwt do not work ) google forces you to use AAB ( APK are still OK but not for long ) Back there with some infos and questions^^
0 kommentar(er)
