Will this break dynamic batching since each asset bundle has its own copy of the same shader? This raises other questions too - for example, since the shader inlcuded in the bundle isn't the exact same shader as the one in my project (it is a precompiled copy), does this break batching? Imagine if I had a custom diffuse shader which I used on all of my assets, and I had 10 asset bundles all containing different meshes/prefabs with materials that used this custom diffuse shader. We need to build our asset bundles for all 3 platforms. When I loaded the bundle, it would use the shader already included in the application (and so it would always be the correct shader, since the shader was already compiled for the current platform whether it be windows, osx, ios or Android). This way, I could exclude the shader from my bundle. My shaders were included in the resources folder and I was able to make the assumption that it would always be there. In 4.x, I used to exclude shaders from my asset bundles. This means that if I am testing in the Editor and have my platgorm set to Android, any asset bundle I load in the Editor will contain pink materials. This is causing some real issues with shaders.! They turn pink, because, as mentioned above, the shader is precompiled for the target platform and included in the bundle (whether you like it or not!). Why? Why can't we disable this? I no longer feel in control of what goes in to my bundle. Now in 5.x, dependencies are always collected. Still, there may be other issues with this path during gameplay.We used to be able to exclude dependencies in 4.x, so we knew exactly what was in our bundles. It does load completely and it does start. One final note of caution: We have not extensively tested the program with the new permissions, yet. Possibly just the KSP.app needs the execute permission while read&write may be sufficient for all others, but this is just speculation on my part. Why this would not be set to "everyone" for an executable by default upon installation I do not know nor understand. The reason may be that the graphical user interface does not give you an option for setting-or even just viewing-the execute permission. We had already tried that without success. Setting the file permissions from the graphical user interface (as suggested on that page and in the referenced link there) does not work, at least for me. Please note, however, that apparently you have to use the terminal command as it is given there.
LOADING ASSET BUNDLE DEFINITIONS KSP MAC MAC OSX
The solution can be found on the page "Known Issues & Self Help" ( ) if you scroll down to the section " Mac OSX Specific Issues". It is necessary to set the permissions of all (?) files and folders within the KSP_osx folder to read, write, AND execute. The solution may actually apply to all kinds of load freeze issues ("Loading Asset Bundle Definitions"), but I cannot verify this. Here it is in case somebody else experiences the same issue. It seems like I have stumbled across a possible solution. Changing the permissions of all the subfolders and the files seems to be unpractical (could only do it one by one).ĭoes anybody have any ideas or suggestions beyond moving the KSP.app? Any help would be deeply appreciated! I have tried setting the permissions of the KSP.app for everyone from read-only to read&write, but that did not change anything either (same freeze). (I can provide more log file info if needed, but I am on a different Computer now.) The log file says basically the same as what was reported in other posts and indicates that part of the contents within the KSP.app package as well as some files in subfolders could not be opened. All other suggestions to similar problems did not seem to fit our situation. This does not help for the non-admin accounts. I have searched the forum and found the suggestion to move the KSP.app to the desktop (or any other place, I suppose) and back in order to avoid the Gatekeeper issue which has been mentioned. (To be precise: In the admin account loading pauses for about three seconds at that stage, too, but then goes on in the non-admin account loading stalls for minutes until I quit the program.) "Loading Asset Bundle Definitions" is displayed and loading does not proceed any further. When running KSP from an account without admin privileges it stalls during loading. When running from an administrator account KSP works fine. I have installed KSP 1.5.1 on a Mac (Sierra 10.12.6, MBP).
0 kommentar(er)
