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"

LogScript:Warning: Divide by zero

When the output log shows:

LogScript:Warning: Divide by zero: Divide_FloatFloat

is there an easier way to identify the exact [÷] node causing the warning or would I have to debug each and every [÷] node until I find it?

The DivByZero isn't causing any problems (presumably the engine is handling it gracefully) but I would still like to resolve these warnings if possible.

Product Version: Not Selected
more ▼

asked Oct 04 '14 at 09:56 AM in Using UE4

avatar image

509 73 66 99

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

1 answer: sort voted first

Hey Ash22-

The node that is causing the warning should have a yellow warning bar below the name. Another option would be to add a breakpoint (Right click the node -> Add Breakpoint) to each divide node. This will allow you to play the level and step through the blueprint, pausing each time a divide node is triggered. This should help you narrow down where the warning is coming from.


Doug Wilson

more ▼

answered Oct 06 '14 at 04:48 PM

avatar image ash22 Oct 06 '14 at 06:38 PM

Will do. Thanks Doug.

avatar image BPANDREW Jan 20 '15 at 12:27 PM

is there an easy way to find all the divide nodes? I'm having this show up in my logs and I'm dreading spending the 30 minutes going over my code with a fine tooth comb - could we get this log entry to be a little more useful?

avatar image ash22 Jan 20 '15 at 12:53 PM

In your blueprint graph:

press CTRL+F and search for each of the following:

"Division" "/float" "/byte" "/int" "/vec"

It's a little tedious if you have 20+ nodes to check but it's the only way.

Just run PIE and debug/watch the Divisor (lower) value of each suspect division node. Eventually you'll find one with a Divisor input value of 0.

(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