Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

BUG: >= (Greater than or Equal to)

alt text Preview 4 There seems to be a bug regarding the >=(Greater than or Equal to) option in blueprint as it seems to be acting like > (greater than) instead. I was attempting to reproduce the inventory tutorial from Unreal's youtube page, but i noticed that for some reason the energy seemed to not preform the jump action despite there being enough value for one final jump. In the top left, you can see using the print string that that every press is only subtracting .05 while the default value (can be seen mid left most) is set to 1.0. I cleared the node and replaced it with another >= but the result didn't change. I changed the Value to be >= to .0499 and it worked

Product Version: UE 4.8 Preview
more ▼

asked Jun 08 '15 at 02:39 AM in Bug Reports

avatar image

6 1 4 5

avatar image TJ V ♦♦ STAFF Jun 08 '15 at 03:39 PM

Hi jail29,

Thank you for the report. I was able to reproduce the issue and I have created JIRA UE-16679. Our developers will be investigating the issue further and we will post back here with updates as we have them.

Another workaround would be to use whole numbers instead. The issue only seems to effect values lower than 1.



avatar image jalil29 Jun 08 '15 at 05:39 PM

I see but the issue for this is that I had been using a simple version in which it would take the percentage of the bar which as you probably know ranges from 0~1

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hi Jail29,

I have looked into your problem and found the culprit, floating point precision errors result in slightly deviated floating values being compared. In this case the decremented value is equal to 0.0999999270 and the comparison value 0.100000001.

Relying on the floating point precision is something you will want to avoid in this case, however there is a Nearly Equal Blueprint node which takes into account an Error Tolerance. Combining this with a Greater Than node as seen in the attached image will give you the desired behaviour.

alt text



more ▼

answered Jun 10 '15 at 02:33 PM

avatar image

136 2 2 4

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question