Leaderboard

No clickbait intended So, after reading some very constructive discussion between @JCarter426 @Kexikus and @DarthParametric in @VarsityPuppet's Ajunta Pall WIP thread, I'm having a little understanding of- why Mono channel would better be implemented rather than Stereo channel for Action, Force Powers, Blasters, and Lightsabers Sound FXs on this game [and I believe in other games too]. It is relevant for the said example to use Mono channel, because- for example, we would want to hear a humming sound of lightsaber on the left side of the speaker when the camera is facing right [something to do with voice panning- if I recall correctly] won't we? And those would not be possible with Stereo channel I'd supposed. The exception would be for dialogue VO on cutscenes- I believe those would be most suitable for Stereo channeled .WAVs or .MP3s as the reason is obvious; for immersion purpose and deep mental involvement of contexts been told. Personally, I am still hoping that Stereo channeled SFXs would be possible to be utilized in-game as me and @CarthOnasty having a plan to alter the Star Map opening sound; to something different than vanilla. The sound has been made, but is still in Mono channel now. Thank you for reading this [if you have been reading this]. Cheers, and may the Force be with you 🙏

Greetings, meatbags. Last time I posted in this blog was quite a while ago, so I thought I'd share what my recording space currently looks like in Texas. The rundown: It's a big ol' closet with moving blankets strung up on the walls and draped above me like a circus tent. The equipment: I've been slowly adding more and more to my space throughout my various moves. First off, the second most important instrument you have (after your voice). I've had three mics throughout my 6 or so years recording VO. I started off with the respectable Blue Yeti USB mic, moved on to the AT2020 and now have landed at the E-100S Condenser Microphone. This thing is good for me to help bring out the natural bass in my voice, but is not markedly better than the AT imo. If you're looking for a good starter mic of your own, I'd recommend the far more affordable AT. Next is the Audio Interface, which is necessary if you're using a non-USB microphone like I am. I use the Focusrite Scarlett Solo, which is a plug and play type setup and has never steered me wrong. The next most important part, is your recording software. Audacity is free and it's what I've always used. Extras: Music Stand to hold your copy (or script), mic stand, stool to place laptop on, LED clamp light to see copy, dog trainer clicker to mark mistakes with loud pops in recorded track. That's all there is to it. Til next time. - UC

I'm going to try scripting a mod. ::fingerscrossed::

So, I don't think I've personally confirmed it in K1, so I can't say. However, from ... other things ... I expect the issue to be the same. I would love to know if anyone does a conclusive test. Just to be clear, the thing is, the engine loads the bumpmap from the TXI ... but only for the texture defined in the model. So, when you are using the appearance to specify a different texture that is not what you have for 'bitmap' in the model file, then it will only do whatever the TXI file for the original texture specifies. So if you are using the same bumpmap on multiple appearances, nothing will really seem wrong. I originally encountered this when I was trying to get different cubemaps on each protocol droid reskin I was doing, and then we actually realized what was happening when DarthParametric was experiencing some crashing issues with his outrageously high quality normal maps. The reason this happens to HK-47 in K2 and not K1 is that the K2 version of the HK-47 model doesn't specify any diffuse textures in the model itself! All NULL. This makes it so that there is no way to get an envmap other than using the appearance.2da column. It's also the issue that makes it so the sith war droid only has a gun texture w/ its 'base' coloration, but with each of the 3+ other colors, the gun model it carries winds up textured with the droid texture and not a gun texture. My personal takeaway has been that it's probably better to remake a model for each custom texture rather than to use appearance.2da, at least until we figure out what the model loader's limitations are... This would actually be a pretty easy/convincing test to run in K1, just NULL out all the bitmap entries for a model, compile it, put it in game (make sure appearance.2da envmap column is set to default) and try to get envmaps via TXI. Or even just recompile the K2 HK-47 model for K1 (for testing purposes) and test using that, since it already has null diffuse textures throughout.

If anything is painfully obvious about its performance, it's the bad taste that The Last Jedi left in fans mouths. Although you do have the large group of fans who simply cannot fathom another person playing their favorite fictional character, but I can relate to that. It's really too bad because Solo is actually pretty good. It's a good (not great) prequel in the same way that Rogue One is. It doesn't try to be more than an entertaining movie. It's not trying to be a massive reboot that has to be a cultural touchstone (ep 7) and it's not trying to subvert every expectation you have (ep 😎