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"

Players can "land" in the corner where two vertical surfaces meet.

I have a game with a lot of intersecting, perpendicular collision surfaces representing abstract skyscrapers. They're all simple box colliders, and the player is using the included CharacterMovement controller. When falling near any of the corners where two buildings touch, the player can air control toward the corner in order to get stuck there. This appears to trigger a landing event, even though all nearby surfaces are completely vertical.

Two such corners where the problem may occur

This happens with step size and perch values set to the defaults, and enabling CCD seems to have no effect. Any ideas?

Product Version: Not Selected
more ▼

asked Apr 23 '14 at 11:48 PM in Bug Reports

avatar image

399 35 39 48

avatar image SFtheWolf Jul 17 '14 at 11:16 PM

Does anyone have any leads on this at all? This bug is still happening for me and remains active in 4.3.

avatar image Alexander Paschall ♦♦ EPIC Jul 18 '14 at 06:17 PM

Hey SF,

Sorry for the delayed response. Thank you for your report.

I have now assigned a technician to test out the issue and attempt to reproduce it. Once they have investigated they will either ask for more information or let you know that they have entered a report. Thank you for your patience.



avatar image SFtheWolf Jul 18 '14 at 06:26 PM

Excellent, thank you!

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

1 answer: sort voted first

Hey, SF!

So, we ran some tests here at the office, and we're seeing the same bug on our end. The good news is: it's not your fault! The bad news is: it's a bug, which means you might just have to wait until we can get a fix written and implemented. I'm reporting the bug now.

As for workarounds, it seems to involve air control - we can't reproduce the bug unless we're actively shoving ourselves into the corner. ...ingame. Trying to prevent or reduce air controlling towards the corner* should work as a stopgap solution, however inelegant.

If you try any workarounds, let me know how they work. I want to see this game working, too!



more ▼

answered Jul 18 '14 at 10:26 PM

avatar image SFtheWolf Jul 19 '14 at 01:13 AM

That's great to hear! Thank you very much for looking into it. I'll be sure to post results here if I attempt to hack it out.

I've noticed that players in the walking state can also continually increase their velocity vector by running into a wall (most noticeable when you have a high speed limit), perhaps that's a related issue? I'll file a separate report for that one either way.

avatar image SFtheWolf Aug 01 '14 at 06:28 PM

Sorry to be a bother, but I was curious if you have a loose guess as to when this might get addressed? I don't mean to be pushy but I consider this bug a blocking issue for releasing my first public beta and am trying to assess my options. I'm targeting the end of this month and I've been unsuccessful finding a workaround that doesn't hurt gameplay so far. (A repulsion field affects all wall collisions, per-frame traces to check for the corner case are temperamental and slow plus they don't handle parallel walls or sticky corners when walking, etc.)

avatar image Jonathan Dorman STAFF Aug 01 '14 at 10:04 PM

Unfortunately, it's not fixed on our internal build yet, so it's very unlikely that it'll be fixed in 4.4. I tried to get in contact with the guy the bug has been assigned to, but he's out of office (it's after-hours here).

I really hate to say it, but I think you'll have to find a workaround for the public beta. I'll be keeping an eye on the bug, but I can't make any promises as to when it'll be fixed. I'm terribly sorry.

avatar image SFtheWolf Aug 01 '14 at 10:37 PM

No worries! I appreciate the info. I'm really grateful you guys are so excellent about communication.

avatar image Jonathan Dorman STAFF Aug 29 '14 at 03:51 PM

Just updating you, SF, we've got this bug entered in the system and assigned to someone. We don't know when it will be fixed, but we're expecting it'll be in the near future.

avatar image SFtheWolf Aug 29 '14 at 11:01 PM

Great to hear! Thanks.

avatar image SFtheWolf Oct 07 '14 at 07:24 PM

This seems to be fixed in the 4.5 preview!! Thank you so much! Was it an issue with actor scaling after all?

avatar image Jonathan Dorman STAFF Oct 07 '14 at 08:08 PM

Nope! As it turns out, the problem was with large-scale Nvidia PhysX meshes. The fix was predicted to take a while longer (around 4.6), but Christmas was early this year and it's fixed in 4.5 (preview).

(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