Inner Circle Update for April 12 2018! (Patreon)

Hey everyone!

I’m a couple days late on this post, but I wanted to reach a good stopping point on the lighting stuff so I could show off the completed vision we’ve been working toward with our lighting system. AltairPL has been making a really heavy push on his end, so he has a lot of progress to show already this month. I also have some updated work from TK and our new sculptor to show off. Ubercharge was under heavy pressure to make progress on a project for his master’s degree, so he’s had to devote serious attention to that this past week, but he will be tackling his tasks starting next week.  

Light Path Expressions and Uber’s Light Compositing System

I’ll start off by saying our ideas for drastically cutting down the workload for lighting are working, and the image above shows just that :D.  All nine of these lighting examples were accomplished with *a single render* that took about 15 minutes.  I was able to put all of them together in about a 60-90 minutes while getting used to the grading controls of the compositing software.  This workflow will absolutely allow a single person to manage the ridiculous amount of character lighting our new art style demands for the remainder of the project.

Here’s how the entire process is accomplished:

• We use Uber’s lighting rig to render approximately ten separate images per pose; one for each light group in the rig (plus one for things like Neon’s lights and dome lighting), thus encompassing all possible lighting situations.  All of the lighting bullshit we went through with the battle test releases pays off dramatically here by the way. I’ll explain below how we’re able to get all the images we need with a single render.
• I dump the renders into my procedural automation network for portraits/battle artwork and wire them up to “Uber’s light mixing system” as I’ve been calling it. From here, I’m able to use the compositing software to simply adjust the lighting how I want. Make the left light red? Done. Reduce the reflection in Malise’s glasses? Done.  Hate the goofy highlight on Malise’s left boob? Roto it out. No need for re-rendering anything!
• Once I complete all the renders for the other poses and add a few additional master controls to the network, I’ll be able to adjust the lighting on *every portrait in the game* with a single set of sliders, and then export all of them at once with any additional post processing. This goes the same for enemies once I get that set up.
• I then use a batch script generator I made in Excel (kind of works like a database for all our portrait data) to create a script that names all of the outputted artwork files automatically. I still have to update this to handle lighting variations and enemies.
• I then batch re-scale for 720p in Photoshop (until we’re in 1080p) > dump files into game folders :D.  Or more accurately, hand off to APL to dump in the game folders.

It was an unexpected detour, but I spent a lot of my time this week furthering TK’s previous research into Nvidia’s Light Path Expressions. This is a coding framework for the Iray rendering engine that makes some great black magic possible (of course, there’s almost zero documentation available so there was a lot of painful testing involved... for anyone familiar with regex it’s similar). Luckily the work paid off. We’re now able to render all necessary images for step 1 of this process in parallel, meaning it cuts the rendering time by 90% for a pose. Tack on another unrelated trick I learned this week and we’re at 95% reduced rendering time for portraits. It’s a huge weight lifted off me considering I’d previously have to be rendering around the clock to make the above system work.

AltairPL’s Coding Progress Report

My part of ToDo list in the monthly update is pretty long, and I was able to only do the small part from it, but I'm still pretty happy with the progress.

April started rather poorly for me, since I had some real-life stuff on my head, but one good thing that came out of it was the much-needed break from coding, especially from all the battle stuff.

My work this month started with the battle sprites overhaul mentioned in the monthly update. Everything is now much cleaner and less convoluted, so adding and changing stuff later won't be as much of a chore as it would be with previous version. It's still not finished though, since one of the plans for it was to move UI/info elements to dedicated classes to make it easier to implement and change visuals, like for example the UI idea Ero posted in the monthly update. I decided to leave it for later and shift my attention to double-teaming, since its visual side was already taken care of during finished part of the battle sprites overhaul.

Now that I think about it, I'm sure we could/should come up with a better name than double-teaming, since the way it's implemented allows for pretty much unlimited number of stacking enemies... and I think Ero already has plans for holds with three enemies at once. Anyway, shortly after shifting my attention to the multi-teaming(?), I've noticed that some hold stuff was still poorly done and it could/would kick me in the butt later, and since it was kinda in line with the multi-teaming stuff, I decided to do both at the same time. The idea was nice, but of course something had to get in my way. In this case, this something was a prototype for H-stat tracking, which was tied to the previous approach. I had only two choices here - either completely yank it out and implement it somewhere along the line or to add it to the current workload. Again, it was somewhat related to the stuff I was doing, so I chose the latter.

To be honest, I think I got a bit carried away with it, but hopefully people who like stats will appreciate it. The prototype was only tracking number of stages of H-skill chains (hold, H-skill, finisher), so I've also added tracking of target body parts for the last two stages (H-skill, finisher). This required some careful planning, but I think it came out rather well... at least for now.

After getting H-stats tracking out of the way, I was able to finish making changes to hold stuff and finally start implementing multi-teaming logic. Since no art dedicated to multi-teaming exists yet, I had to use some old enemies and art for testing by making copies of all needed database elements and adjusting it accordingly. After that it was pure coding, testing, coding, testing, ... Suffice to say, conditioning for enemies joining the fun seems to be working just fine, so now I need to focus on fixing some more or less minor issues and come up with some neat ideas for the behavior of enemies who are already holding an actor when another joins in, such as pausing or looping one chain skill if an enemy that can join the fun is available. Oh, and I must not forget about adding support for inanimate spawned “enemies”, like handcuffs, which shouldn't be able to act in the first place.

Well, it was going well so far, so I really hope nothing blows up in my face and I'll be able to finish all the battle stuff and start something else from the ToDo list before the next IC update.

Ven and Splicer Overhauls

TK has finished remaking the textures for Ven’s legs, and he is nearly finished with the new model for her arms. The texturing process for these will be a lot simpler after having done the legs. I haven’t gotten my hands on the final leg textures yet, so the only screenshot I have is a low-res one of TK’s from Substance. I’ll probably rough em up some more once I get them into Daz :D. That said, the new textures get rid of all the baked in gradients/shadows that don’t make sense for physically based rendering.

• Ven Legs Preview
• Ven Arms Model

Our new sculptor has been plugging away at the Splicer assets, and she’s has finished the model we showed in the monthly update. She’s since been working on variations for materials.

• Splicer Material Variation WIPs 1
• Splicer Material Variation WIPs 2
• Camo material close-up

That’s about it for now! I always feel kind of meh when the majority of our work for an update goes into technical stuff, but hopefully the value of it is evident :D. Thanks for bearing with us through it!