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"

Why do blueprints act differently in the editor preview?

I've experienced this twice now on two different major projects (both Paper2D if that helps).

The physics, timing, line traces, everything acts completely differently in the editor than in the stand alone game. Is there a reason?

Product Version: Not Selected
Tags:
more ▼

asked Jan 31 '15 at 03:48 AM in Bug Reports

avatar image

The Britain
73 19 14 18

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

2 answers: sort voted first

Because the framerate is by default uncapped in the editor but capped to 60 FPS outside it, which means things getting done every Tick are probably happening less frequently, especially for a Paper2D game or other one that's capable of high FPS on a beefy machine (my game gets 115FPS in editor, capping it at 60FPS outside of it makes a LOT of stuff work differently).

more ▼

answered Jan 31 '15 at 11:32 AM

avatar image

RhythmScript
243 20 25 36

avatar image Shadowriver Jan 31 '15 at 11:37 AM

Thats why code should scale any per-frame data changes to delta time and code in engine do that and i don't know what this has to do with line trace.

avatar image RhythmScript Jan 31 '15 at 11:41 AM

Well it depends on the trace. If he does a trace outward from base to tip of an axe every tick to detect hits, he gets half as many traces and it appears as though the trace no longer works properly; I ran into that exact same problem! And its not as though delta time compensation can fix the number of traces...

avatar image The Britain Jan 31 '15 at 09:51 PM

This is exactly one of my problems.

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

Non-editor build does not have editor code, for example they don't have code that is made for development like debugging and monitoring code. That main reason why there difference in behavior. In this case each issue need to be treated individually there possibility some of them are bugs and not suppose to happen, so make more detailed question(s), whats so diffrent in physics, timing and line traces?

more ▼

answered Jan 31 '15 at 11:21 AM

avatar image

Shadowriver
37.8k 937 172 1123

(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