At this moment we do not have plans for another 4.6 hotfix, so the “Color Information Clamped to a of 1 in Cascade Color Modules” issue you mention is slated for the fix to be in 4.7. Although if you are using the source code for GitHub, I could find the commit to the master branch which contains the fix. Let me know.
If you weren’t aware, there is a workaround listed for the issue: “You can graph it and select the point you want to change and then set value to any number, but it will be clamped back to 1 if you adjust in Details Panel.” Not ideal I know. Sorry for the troubles.
If you weren’t aware, there is a workaround listed for the issue: “You can graph it and select the point you want to change and then set value to any number, but it will be clamped back to 1 if you adjust in Details Panel.” Not ideal I know. Sorry for the troubles.
[/]
I just use the color picker!
The color picker values are not weirdly clamped and you can enter the values directly like you would normally
**
Github Fix**
For anyone with a Github engine you can apply the fix yourself here:
https://github.com/EpicGames/UnrealEngine/commit/1e085ee2ae42dff7a83e39722346962d7b2d4d34
♥
[=;193869]
Not only do I second this question, I would also like to add:
If I accidentally put a loop in my game, I understand the detection and reporting of that loop is important. It keeps me from crashing my game, however, for the love of the gods, please do not replace that with infinite popups telling me that I have a loop. It is obvious that Unreal detected it, so please terminate the process.
Yeah I have issues with while loops in BP, there are instances when Ive wanted to use them and simply cant because they hit the iteration limit in a split second even when I try to put a delay in there. There are instances when you want a loop to runaway for awhile only to come back when the condition has been met, its just a shame that the iteration limit is the same on both for and while, if I raise it for while then I could potentially put myself in trouble with for loops I dont want to run for so long.
I actually suggested a detection in the closed Beta testing because I had put while/for loops in construction script and it was causing my BP to crash out when I opened it, making it an irreversible error. I think I did find a way to stop the construction script of a Blueprint through its properties but that option seems to have been removed in the right click menu update for the Content Browser
[=MonsOlympus;193979]
Yeah I have issues with while loops in BP, there are instances when Ive wanted to use them and simply cant because they hit the iteration limit in a split second even when I try to put a delay in there. There are instances when you want a loop to runaway for awhile only to come back when the condition has been met
[/]
You could use a Gate-Loop instead, or write your own “while loop with delay” (Double Click the loop node. That works great btw).
[= Ellis;193657]
If you weren’t aware, there is a workaround listed for the issue: “You can graph it and select the point you want to change and then set value to any number, but it will be clamped back to 1 if you adjust in Details Panel.” Not ideal I know. Sorry for the troubles.
[/]
Ah okay, thanks ! Wasn’t aware of the graph workaround!
[=;194015]
Ah okay, thanks ! Wasn’t aware of the graph workaround!
[/]
It’s a lot easier to just use the Color picker
That’s the solution I came up with that has been working great for me
**
Github Fix**
For anyone with a Github engine you can apply the fix yourself here:
https://github.com/EpicGames/UnrealEngine/commit/1e085ee2ae42dff7a83e39722346962d7b2d4d34
[=;193990]
Different loop options are great, but that popup is annoying at a level words can’t explain.
[/]
My advice was only meant to solve the “Loop till condition changed”-algorithm, which simply will not work with a while loop. The while loop ignores a delay/timeline in the loop body and iterates simply so fast, that you reach the infinite loop threshold nearly instantly.
[=;193857]
Does this fix all the random crashing people are getting?
[/]
Hi , it will fix some crashes, but I will need more details about the crashes that you are experiencing in order to investigate that further. Can you please submit a bug report to answers.unrealengine.com so that I may assign a technician to look into it further. Please fill out your report with your crash callstack and as many details as possible to help our staff.
[=;193857]
Does this fix all the random crashing people are getting?
[/]
It did not get the crashes I am getting, see questions/145650/engine-46-and-451-crash-like–on-mac-os-10101.html
That is on Mac OSX 10.10.1. BTW when I run on windows using Parallels on the same machine, I don’t have any crashes (but it is too painfully slow to use…)
The first thing you can do is go into Edit -> Project Settings -> General and then set “Maximum Loop Iteration Count” to a higher number if you know that’s what you need. Or, you can also try breaking up your loops if possible, avoid using While Loops and look out for For Each Loops in which you are adding things to the array that is being used for the loop.
I would agree that the infinite loop pop-up messages are not useful and I have entered a report that they need to be changed. The reason you are getting so many pop-ups is because it is reporting every infinite loop. So if you have an actor with 3 loops that trigger the infinite loop error and then you have 100 of them in a level, it will give 300 error messages. I’ll see to getting that fixed and made into one message that lists all of the bad loop locations.
Thank you for you feedback, please let me know if there is anything else we can do to improve your experience with UE4.
when can we expect the “import layer info from file” on landscape to stop crashing the engine, it worked in 4.5, now I cannot import layers from world machine to my landscape cause the editor crash, kinda suck to be stuck with a pitch black landscape…
