x

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"

Events Begin/End Cursor doesn't fire when mouse is fast.

Im trying to use the events Begin/End Cursor in a Colision box. It works, but it just doesn't fire if you're moving the mouse too fast. I've been testing the ''speeds'' that trigger the event, and its kinda good for me, but i want to know if there is something to fix this.

Product Version: UE 4.9
Tags:
more ▼

asked Jan 03 '16 at 04:32 PM in Blueprint Scripting

avatar image

DevilKaito
11 3 3

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

1 answer: sort voted first

This is a bit old but in case someone runs across this like i did. A higher framerate should help, but if you dont have one a solution(and the only one i can think of) would be to do the detection manually, on tick do a trace (to detect cursor begin/end cursor over, this is likely what the engine is doing anyway.) then

to save the previously known mouse location from the last tick and get the current position from this tick then subtract them from each other to get the difference, divide by 2 to get the half way point of that difference, then add it back to one of them to get the in between point(you may have to add it to whichever one is closer to 0,0). then do a trace from that position before doing the trace from the current tick. this should give you a in between trace but it will double the number of traces you are doing per tick. you can also add in a if statement and compare the current ticks mouse location from the last ticks mouse location and check the distance between them, if its too small dont do a extra trace, if its far enough apart then do the extra one. Depending you can even do 2 extra traces by dividing by 3, 3 by 4 etc. but i imagine this will start to get heavy depending on whats happening so testing required.

For most cases i dont imagine this would be vary useful but if you must get that in between trace(like a laser that cuts/hits all actors under the mouse) then this i think would be a suitable solution, though i cant say whether there is a better option or not, this is just the best i can think of.

Maybe a bit complicated? but if you need it you need it. if you can get by with potentially missing over some detections then im not sure id bother with this.

more ▼

answered Aug 22 '16 at 02:48 AM

avatar image

Jener
1 1 2

(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