Soft Particles, Dynamic Lighting and DX9 wonderfulness in FW:ToW
-
Nice being able to see everything coming together a little at a time, what’s cool about this in particular, is that it also clearly demonstrates what’s missing from freelancer, things that I wouldn’t have been aware of without seeing this. I probably would have just played it after release and thought, wow, this looks different, but wouldn’t have been able to fathom why. You make a great team guys.
I have a question about the plugin that you might eventually release. When you say plugin, do you mean something that will just get dropped into the EXE folder and work with no necessary tweaking? As in it could just be applied to vanilla freelancer and make a noticeable difference like we see in your deferred lighting video.
-
-
That’s what I’m trying to establish, how much of what we see in the dev videos is to do with the effects that they are creating and how much is due to what will be the eventual plugin.
i.e - will freelancer look all that much different to what it already does in vanilla form with just the plugin.
-
as there are already lights and even dynamic lights in vanilla fl - yes, it will. however, if you want all your projectiles and missiles and flares and everything to emit light to nearby objects, you need to code it. it could even work with the fl you have now, problem is only, you have neither specular support nor will all lightnings show up or show up correctly.
-
What Gisteron said.
Different additions will mean different amounts of work. Bloom will work out of the box, obviously. Color correction needs per-system TGA gradient ramps created, so by default nothing would happen. Specular lighting is enabled by default, but for best result you will need to create your own specular map for all models (planets included). Soft particles need to be added manually on VisEffects. Dynamic lighting uses FL’s lightanims, so the few places where they are used will benefit from the new tech, but for the most part additional light sources would need to be added manually for the effect to really stand out.
Eventually, normal mapping will also require manual addition of your own normal maps.
-
This page has all the info you’d need:
http://http.developer.nvidia.com/GPUGems/gpugems_ch22.htmlTake these effects and apply them to systems.
-
Thanks for clearing that up, I had a feeling that it might be that way. Awesome for modders with knowledge of ALE’s and such then, but slightly less awesome for others. Awesome with the potential for sauce! :lol:
-
Systems as in Li01, Li02, etc.
-
confused so you mean a modder would have to define in the system file a few values on how to handle the frame rendering? does the plug-in read out a new syntax you have to add or is there a configuration file where you define all of the corrections to each of the systems? something like that? well, when you release it, there will be a usage guide xD
-
- You make a 256x1 gradient from black to white.
- You apply filters to it in Photoshop or your favorite image editing program so that it looks as you want in the game (easiest way is to make a screenie and then apply filters to that screenie until it looks good, then copy all the filters to the gradient).
- Save in data\textures\color_correction as a TGA with the name of the file being the nickname of the system.
- Bingo!
So to tint Li01, I’d make a screenie of the system, edit it in PS, apply all the edits to a gradient, save the gradient as Li01.tga in that folder and it’d be good to go.
Absolutely nothing to do with ALEs or shader programming.
-
Nova, cut with the crap. Thank you.
