Do you also do the rigging and texturing? Or is rigging and texturing different departments? I assume the rig is the same for every Valk skin, but this one has a helmet :)
rigging is another department, but i did the texturing myself
Do you also do the rigging and texturing? Or is rigging and texturing different departments? I assume the rig is the same for every Valk skin, but this one has a helmet :)
rigging is another department, but i did the texturing myself
Try here, it's where I started: https://www.respawn.com/careers
Hey thanks mate, appreciate the appreciation, but its not a one man show, lots of credit goes to Cristina Laviña for the killer concept, and Moy Parra for the kick ass custom animation. Im just the guy that made the 3D model <3
I'd be pretty annoyed if when ever I played some random just told me what they didn't like about the game. I'm sure he just wants to play and not host a feedback panel.
Maaaan I’m just happy when the first words out of a teammate’s mouth aren’t, “yo can I get an heirloom?”
That’s easily the number one thing people say when they recognize I’m a dev. Gg chopsticks
Used to be either a dev or someone on your friends list that had played Apex before. Now it is just Dev boxes
What they said. Just Devs now.
Here I go crying for the fifth time today. The community response to this is so heartening to see. Thank you for sharing with us, OP.
Glad to hear you're still with us.
These aren't my words, but I would like to say them given the timeliness of the issue:
"I would be sad if you were to pass away"
https://twitter.com/tangentiallogic/status/1005716376651063296
Yeah, that's BiGRiG
that's MR BigRiG to you! :D
It looks like it has been recently (since a few days) fixed. I got heavy microstutter starting with 191 fps on 200 Hz monitor. Since a few days it is butter smooth and I play on locked 197 fps. Don't know how it looks like on 240 Hz though. u/ricklesauceur can you please confirm that this problem was addressed?
yes
Another question- considering that the game is cross platform, why cant xbox/ps4 players plug and play MnK similar to fortnite and warzone? As long as it identifies them as MnK on xbone/ps4 and puts them in cross platform lobbies i feel that is fair? However, i know this can be hard to implement potentially, i was more specifically curious if there has been any talk about this in the future?
Edit: also if it was MnK compatible then potentially that could open the door for console (extra) binds
I actually have no idea what this would take. I've not heard anything about this internally, but it may have been tackled and put to rest before I started - I've been on the team about a year. I don't think there's a big demand here, so maybe it's just a case of being super niche. I do know that it doesn't "just work" but I have no idea how hard it would be.
Core interactions in terms of controller functionality are not something we take lightly, so we tread very, very carefully, since a lot of players have muscle memory built up over thousands of hours that we don't want to mess up.
Why not just let them keybind controllers the same way we can remap them on PC?
So knowing that "it's complicated" responses are generally shitty, I'll nevertheless respond with, "it's complicated." Fundamentally, there's a very different core UX expectation with a controller. First off, you're limited to 16 buttons. And the core expectation around how those buttons work is quite different from MKB. With a mouse, there's an expectation that "clicking on a thing" will do something. Controller logic in this regard is quite different; we try to avoid having players hover-over-a-thing-and-press-a-button. Now, sometimes, that's unavoidable (e.g. deathbox looting), but it's generally not great. In most places, we try to make it so that you see that a button - e.g. X - is bound to some action, and when you press X - anywhere - something happens. Now, this leads to some weird behaviors too because of core aspects of our UI framework (and trying to support both controller and MKB simultaneously and fairly seamlessly) where hovering over a "button" (on screen) and pressing...
Read moreNot my area of the game, but I agree with this and have flagged it internally to try to get some eyes on it from the Legends team. The limitations around controller buttons is definitely frustrating, and there's never a perfect way to map 16 buttons (IIRC) to the nearly infinite options offered by MKB. We try not to have options for everything, because that introduces UX issues of its own, but in some cases where it's clearly interfering with utility, I think it's warranted. I'm a console player myself, and I can say we're definitely aware of many of the common controller buttons frustrations ("I wanted to res my teammate, but instead I opened the door." and "I wanted to reload but instead I went to res my teammate" etc) and it's a constant debate between interfering with learned behavior and working to tune usability.
Core interactions in terms of controller functionality are not something we take lightly, so we tread very, very carefully, since a lot of players have muscle memory ...
Read moreThat's soooo cool. I would wear that everywhere! The people on the bus would be mad :)
Thanks. Forwarding this on.
Hate to break it to you, that's a bug sitting in the backlog for a few months...
Ah yes. This is how I found out about the harvester beam too. It was a ranked game too.
This is a consistent issue at the start of each season for some players but it's not one that we've ever been able to successfully reproduce internally. We've tried every theoretical combination around leaving matches, downed enemies, downed self, disconnects, etc. And they never get out of sync. But some players report this near the start of every season. There's no logical reason for this to happen - the lines that make the updates to these stats are basically right on top of each other. I wish I had a better answer. We know it happens. But it's still not at all clear why. And there's nothing I'd change about the way that we handle this flow from a logic perspective. I can definitely say it's not a case of us ignoring it. I'd love to fix this. But I just don't know what to actually "fix."
So I'm gonna sign off, but I did want to say thanks to everyone who responded. It's a pretty amazing community here, but also one that's a bit intimidating. And also a bit like drinking from a firehose, so I apologize for people who asked questions that I didn't respond to. I read all the replies, and I'm sorry I couldn't answer all of them. There were also some pretty great suggestions about things that I had not thought to test that I will try before S11.
Prior to becoming a game dev I worked in a field where "effort" didn't matter much. It was purely about results. So I can appreciate that saying, "I tried to fix this but couldn't..." doesn't necessarily mean much. But when I see bugs like this one - or more major ones like someone missing a 20 Bomb or 4K badge - in areas of the game that I am one of the main devs for, it bothers me a lot. I play this game a lot (I'm still pretty bad though), and it bothers me as a player. I care deeply about the areas of the game that I do work ...
Read moreI think I might know the cause, when Valkyrie came out my friend and I were messing around in the firing range, before joining any matches, and I already had thirty some kills at the beginning of the first match playing the character. So from my experience it’s from killing people in the firing range before joining any real matches
Firing range bug was a separate one. And it was unique to Valk. Basically, if you triggered Valk's ultimate, we assumed it counted as a "landing" - same as if you jumped out of a plane. And so once you jumped, it was like being in a match.
I don't think u/AlcatorSK is talking directly about this, but what about matches that overlap seasons?
You said that everything is driven by timestamps. Well it's entirely possible (and we see posts about it on Reddit) that a player can start a match in one season and have it end in the next season. Therefore any kills made in the overlapping time period of the match would be credited to the next season. Is that correct?
EDIT: Forgot we're talking about S10 exclusive, Seer. This wouldn't help with OP's case
Possibly. Except that we see this with new legends - like Seer - that are literally unable to be played in the previous season. If it was every legend EXCEPT the previous one, it would make sense. But that's not what is happening.