Otherwise a video is not the best way to explain the issue. I can't make out anything in that video - you probably might want to slow your actions down by a lot and also annotate/highlight/freeze frame things in it. Push-to-mute, however, also seems similarly broken.Īlso: I believe that push-to-talk has not functioned correctly for some time I believe at least as far back as 27.2.4 (though the issue presented slightly differently). The mute and unmute hotkeys seem to work correctly. I've tried removing those permissions and re-granting them, but it does not seem to have any effect. I've made sure OBS has Accessibility permissions as well as Input Monitoring permissions. With or without OBS having focus, press the hotkey observe no response in the audio mixer or in the output.In Settings->Hotkeys, set a push-to-talk key for the audio source.Add a source with audio (for my testing, I used an Audio Input Source associated with my built-in microphone).In the past, I've seen it momentarily engage the audio source for a fraction of a second and then immediately mute it even if the button is still pressed, but that behavior doesn't seem to be present now. It neither mutes nor unmutes the audio source. Currently, on my system, the push-to-talk hotkey seems to have no effect whatsoever. muting the audio source unless the selected button is currently pressed down. The Alpha of the first flipbook is the transparency, and the alpha of the second flipbook contains the emissive fire part.Push to talk should operate correctly, i.e. I didn’t see any normal map or motion vectors. At least, I guess that they are lightmaps. The channels RGB1+RGB2 contain 6 lightmaps in total (if you ask yourself “why 6 lightmaps?!” please follow this link). I can see this also in the data: There are two flipbooks for the same smoke/explosion. As you can see, there is a smoke layer and on top a perfectly fitting fire layer: Source: Visual Effects in Star Wars Battlefront II The separation of smoke and fire was shown in the official blog post about their VFX. I guess one uses a smoke-texture and the other one a fire-texture (more about this below): Source: Starwars Battlefront II This gives the whole effect a good depth. I was surprised how many particles the explosion used and how volumetric the “geometry” is. Here you can see the wireframe of the explosion particles (pink) some blue trails and on the right some blue stuff which I don’t know what it is :D But the important part is the wireframe because as I mentioned before: The effect consists of more single particles than one would think. Some are unique: They show for example how smoke/fire builds up and then dissolves over time. But in fact, it’s quite more complex than that! Explosion from Starwars Battlefront IIĪlmost all VFX textures are gathered in one huge atlas (12288x8192px, DDS = 96 MB). At first glance, it might look like 1 flipbook put on 1 particle. I’ve checked out some VFX (but mostly an explosion) from Star Wars Battlefront II and wanted to share the gained knowledge.
I hope you like it and let me know in the comments what you think about getting back to the roots! :) Battlefront II: Boom Sometimes I see cool threads on Twitter and I always wonder: What if Twitter shuts down or what if the account gets banned for some reason? Putting stuff on your own blog (maybe in addition to Twitter/Mastodon/Facebook … lol, Facebook :D As if someone would still use it! :’D) gives the information more security.Īnd that’s why I’d like to convert a Twitter-Thread I did in 2020 about Explosions in Battlefront II into a small article here on my blog.
This is also a way to secure information for the future. This means: If I observe something cool in a game, I’d like to have the mental freedom to put it into a post even thought it may be only one or two images and without the pressure of having to create a video. And also took away a bit of the fun because it felt more like work and created a barrier: IF I’d start a new article, I knew it will cost A LOT of time – this mountain of work could make me hesitate to start at all. This resulted in longer (better) articles, but also created pressure to never release something smaller again. While an article from the beginning did just cost some hours to write, the later posts could cost weeks or even months to put together.
I had the honor of being invited to give a GDC talk in 2022.Īnd second: While my articles were tiny at the beginning, they grew more and more complex, and then I’ve even started to create a video for each of them (#overhead)!
0 kommentar(er)
