Dine kommentarer
I apologize if I came across a little bit terse, it certainly wasn't my intention.
The issue of not having time to fix it aside - changes to the compiler in SF has a tendency to create knock-on effects, causing bugs and issues in unexpected places, which is why I'm very wary of making changes in the 4.x version. I've also pretty much removed the entire build -> prepare -> package -> export -> upload pipeline for it, so other external things might break, where assets go missing, or were compiled in the wrong version, and so on.
It's a risky move on my end, which has a potential to break SF for all customers still on Unity 4, leaving me with more bugs to fix, in a time where I can't spend much of it for fixing bugs.
If you want to get this fixed as soon as possible, the most straightforward solution I see is this:
Give one of your coders an hour to code an editor script, that allows you to select a shader, and press a button to make it move that line to the correct place.
It's very straightforward, since the shaders are essentially text files.
For the coder:
1. Add a button to Unity's menu bar (MenuItem)
2. Detect which shader is selected in the project view (Selection Detection)
3. Read the file into a string array (File Handling)
4. Find the line you wanted to move, and move it
5. Write the string array into the file
For the user:
1. Compile the shader in SF
2. Select the shader you just modified
3. Press the button or hotkey that the coder added to Unity
I'm guessing it's not the answer you wanted, but I hope it helps anyhow
Joachim
The issue of not having time to fix it aside - changes to the compiler in SF has a tendency to create knock-on effects, causing bugs and issues in unexpected places, which is why I'm very wary of making changes in the 4.x version. I've also pretty much removed the entire build -> prepare -> package -> export -> upload pipeline for it, so other external things might break, where assets go missing, or were compiled in the wrong version, and so on.
It's a risky move on my end, which has a potential to break SF for all customers still on Unity 4, leaving me with more bugs to fix, in a time where I can't spend much of it for fixing bugs.
If you want to get this fixed as soon as possible, the most straightforward solution I see is this:
Give one of your coders an hour to code an editor script, that allows you to select a shader, and press a button to make it move that line to the correct place.
It's very straightforward, since the shaders are essentially text files.
For the coder:
1. Add a button to Unity's menu bar (MenuItem)
2. Detect which shader is selected in the project view (Selection Detection)
3. Read the file into a string array (File Handling)
4. Find the line you wanted to move, and move it
5. Write the string array into the file
For the user:
1. Compile the shader in SF
2. Select the shader you just modified
3. Press the button or hotkey that the coder added to Unity
I'm guessing it's not the answer you wanted, but I hope it helps anyhow
Joachim
Well, like I said, I'm not supporting Unity 4 anymore, and even if I did, I don't have the time to make that change now.
It is fixed already, for Unity 5. It's not my fault that you're still on 4
It is fixed already, for Unity 5. It's not my fault that you're still on 4
Ah, hm, odd. Not sure what might have caused that :/
Mail me and I'll give you an old version if you like
Mail me and I'll give you an old version if you like
You can't use the Unity 5 version of SF in Unity 4, you'll get issues like this.
And yes, I'm no longer supporting Unity 4 SF, which is why I'll always recommend going Unity 5!
If you want the old version, download it through Unity 4, and you'll get the latest compatible version
And yes, I'm no longer supporting Unity 4 SF, which is why I'll always recommend going Unity 5!
If you want the old version, download it through Unity 4, and you'll get the latest compatible version
Unfortunately I'm not supporting the 4.x versions anymore, although this has been fixed in the Unity 5 version of Shader Forge.
I recommend creating a backup of your game, then open it using Unity 5 and see if anything breaks. The upgrade is often much easier than you think, plus, in Unity 5 you have all the pro features of Unity 4 for free
I recommend creating a backup of your game, then open it using Unity 5 and see if anything breaks. The upgrade is often much easier than you think, plus, in Unity 5 you have all the pro features of Unity 4 for free
Oh dear. I'll need to make a vector graphics plugin soon then
I'll look into this in the coming week - seems like it's one of the more commonly requested features now :)
Not sure what to do there. I recommend updating to Unity 5, and use Unity's light probe & PBR system instead
Unfortunately, no. It has too many implications that would require a *huge* rewrite of the shader compiler, I'm afraid :(
Kundesupport af UserEcho
Which version of Unity and SF are you using?
And what platform are you targeting?