We now have 2 cloud layers and 9 cloud types. Each condition will have 2 cloud layers which we will dynamically blend between. Each cloud layer has lighting settings, cloud density and weighting of the different cloud types. The layers are called high and low although the altitude is actually set up elsewhere in the cloud definitions file so clouds of any altitude can be used on any layer. As a rule though, I intend to use the high layer for higher cirrus style 2d planes and the lower layer for the 3d billboard clouds.
The clouds are fully dynamically generated, move in the wind and fade in and dissipate using a new optimised shader Kevin has created. We are also looking at morphing tech for the 3d clouds.
2d planes
- altocumulus
- cirrus
- cirrocumulus
- cirrostratus
3d billboard clusters
- stratocumulus
- cumulus
- stratus
- cumulonimbus
- stormcloud
The cloud definitions file specifies the meshes used for each of the cloud types above, I have between 6 and 12 meshes for each type currently. The file also sets the min and max altitude at which they will spawn, we will add rotation and scale variation in here later.
The texture is now one complete map with red - diffuse, green - thickness, blue - dissipation, alpha - opacity. Then a second texture with 3 channels of nmp on the thicker clouds that need it.
There are still several issues to sort but here are some early images to show progress.
Starting a new thread to track development of the ancillary multiplayer systems. All of these systems relate directly to console platforms although some also can be applied to PC. It is typical that each platform is implemented differently (eg. on consoles we use the 1st party API methods to deliver functionality) and on PC it very much depends on (a) if a feature will be implemented then (b) which tech will be utilised (eg. custom built vs GFWL vs Steamworks etc). When it comes to publishing console titles, all of these systems have rule sets strictly defined by the 1st parties (eg. Microsoft and Sony) and compliance is required in order to deliver a product to market.
In no particular order, such systems include:
Sign in/sign out handling
Xbox 360 session handling
Xbox 360 game reporting
360 Live membership tier (Silver/Gold) restriction handling
360 party support
360 achievements
PS3 trophies
Friend lists
Matchmaking (eg. matching players together via player level, custom searching, handling different content such as DLC)
Rich presence
Game invitation handling
Leaderboards/read/write/caching
Online data storage/read/write/caching
VOIP support/muting
Parental controls (eg. PS3 regional/sku age restrictions for multiplayer areas, 360 content restriction privileges)
I've locked this thread for developer updates so that progress is easy to follow (Devs please add your contributions throughout the project). WMD members are welcome to open discussion threads in the forum for Q&A.
[/spoiler]
![[Ooooo]](/images/smilies/nuevos/sorprendido_ani1.gif "Oooooo")
Rain
For phase 1 of the rain we added car spray and the wetness values to the conditions. Moving forward we need to add:
phase 2
- Rain fall
- Rain drop splashes on track
- Track spec and reflections increase with the track wetness value from tweakit, also needs to be masked off in tunnels.
- Drying line
Phase 3
- look at increasing GSI on all mats as it gets wetter, GSI needs removing from cars and balancing better for dry conditions as a start point.
- standing water, maybe develop this alongside the reflections on track as it can tie into the wet mask.
- thunder and lightning. effect, triggered light and sound.
Phase 4
- Windscreen effects. Rain drop build up that gets removed by wipers. Need to work out the best approach.
- rain drop effects on the paintwork
- Side and rear window effects
- camera droplets similar to windscreen tech. These need to go in and out of focus as track side cams zoom in and out
We have also added rain fall particles for light rain, rainy, stormy and super storm. The density of rain, speed and angle all increase the stormier it gets. The rain also angles with camera direction to give a sense of speed when going faster. I had a few issues when blending to non rainy conditions but these are all sorted now and the transitions work much better.
![[babas]](/images/smilies/babas.gif "Babeando")
Como van las versiones de consola!? Han mostrado algo más bajo ellas!!?? 
Pablopictures escribió:¿Se sabe para cuando sale más o menos? esta bien que implementen tantas cosas, pero no si a cambio tardan media década en sacarlo, llevo mucho tiempo esperándolo y uno se impacienta
denis74 escribió:Han comentado algo sobre la versión de consola:La versiones de consola se verán muy similares a la versión de PC. La mayor diferencia es la resolución (las consolas serán limitadas a 720p). Algunas texturas también serán a baja resolución debido a la falta de memoria de video en consolas, pero las buenas noticias es que, de todos modos, a 720p realmente no necesitas esas texturas a ultra alta resolución de PC.The console versions will/do look very similar to the PC version. The major difference is resolution (consoles will be limited to 720P). Some textures will also be lower resolution due to the lack of video memory on consoles, but the good news there is that at 720P you don't really need those ultra high res PC textures anyway.
Parecía que la versión de consolas iba a quedar bastante desmejorada en comparación con la de Pc, pero por lo que comentan parece que no va a ser para tanto. Sólo queda ver las diferencias que habrá en las físicas... ![[oki]](/images/smilies/net_thumbsup.gif "Ok!")
Update. I've been working a bit on console leaderboards, focusing on 360 for now. Initially we will have one leaderboard per track since 1st party limitations won't permit a complete set of per-car/per-track leaderboards. Later we'll see what we can do about extending it a bit (such as adding an additional leaderboard per car class). Anyway, any implementation will be mostly app-side and my focus has been on adding the core online tech.
Where we are at the moment (nothing checked in yet, just a huge P4 shelf CL), is I've created an initial set of test leaderboards and submitted them to Partnernet. With some fakery of app-side implementation so I don't waste time having to run laps, I'm able to upload and download scores and individual sector times for the local player. First task was to split out the PC-centric Stats class into platform specific parts, then ensure that I remain compatible as much as possible with existing code (such as the stat cache and post-read/write app-side actions). This is all fine, or at least should be. Then I added the 360 API calls necessary to read and write the stats themselves although because of the way Live works and that we don't have full 360 gameplay working yet, I needed to hack in some special XSession code (all leaderboard API write calls must occur between XsessionStart and XSessionEnd calls otherwise Live rejects the attempt). Normally these XSession calls will occur at the start and end of gameplay and when they are implemented I can remove these hacks.
Next I am looking at ghost data support; for 360 we will be utilising Live's Game Clips. When we define the configuration of each leaderboard using the Game Config tool, Microsoft allow us to specify how many data attachments may be associated with a leaderboard. The limitation here is per-title storage space so we may have to be quite restrictive on how many data attachments will be supported per leaderboard. We haven't yet calculated that out and the actual numbers will come later once we know our total number of leaderboards, size of game clips and so on.
As per the Stat work, the first task has been to split out the PC-centric parts of the Storage Manager into platform specifics. I've already cooked up the ghost data upload code into a useful sample today and should just need to plug that in once I've finished with the restructuring work.
I'll update more as I progress.
denis74 escribió:Mola tu muñecote de la esquina,jeje
Bueno, la IA que tenemos ahora es temporal y están rehaciéndola por completo. Así que lo que tenemos es lo que vulgarmente se llamaría un "parche" de IA.
Dentro de cosa de un mes estarás totalmente reconfortado al ver la nueva IA, que será como si luchases contra humanos. La experiencia hará un giro de 180 grados.
Mientras prueba con los parámetros que posteé allí en el apartado que hay sobre ello. Lo que pasa que en unos coches esos parámetros funcionan mejor que en otros.
