![[oki]](/images/smilies/net_thumbsup.gif "Ok!")
The 'Share' button (currently disabled) is designed to allow you to save the current event setup to your Vault (which also contains all your replays, photos, tuning setups, liveries etc..) and then share it with friends (useful if you want to be the 'event organizer' and distribute a time trial out to friends or to give particular settings to a potential new recruit to your online racing team) so hopefully this is along the same lines as your Quick Select Sets idea (since you'd be able to 'load' it from the Vault also). I know this feature should be labelled 'Save' in that case but I thought it'd be too confusing to call it that in this iteration otherwise it might be confused with the standard 'save' option elsewhere (and then there'd be reports of "Andy, the save function doesn't work!"
![[sonrisa]](/images/smilies/nuevos/risa_ani1.gif "sonrisa")
Rodie escribió:Me alegra leer que lo del tema físicas en las consolas parece ser que se están poniendo las pilas, me había hecho perder un poco de interés por el juego este aspecto. El tema gráficos para mi sería más secundario.
![[360º]](/images/smilies/nuevos/vueltas.gif "como la niña del exorcista")
El volante que tengo es el de Microsoft pero en pc no tiene forcefeedback. Una pena. Quizás lo venda algún día pero me esperaré a Septiembre-Octubre 2013 a ver como rula en pCARS Xbox360 
![[beer]](/images/smilies/nuevos2/brindando.gif "brindis")
denis74 escribió:Calla calla que con tus comentarios sobre lo bien que va el FFB en pc me están dando ganas de pillarme un Logitech
Stat writes are now working correctly on 360. Ghost data is also uploading on 360, however I've hit a couple of blockers at the moment. IainR will divert from current activity to write the XSession wrappers (replacing a local hack that has outstayed its welcome) and once they're in (and with some work from MichalR to adjust some app-side stat flow), I should be able to properly complete the ghost upload work for 360. Writing the ghost download code should be fairly simple (already started but paused until the uploading flow is correct).
While I'm blocked on 360 I'll start work on PS3 leaderboard support but will probably be flipping backward/forward between the two platforms as other team members progress their work.
. 
Ardo en deseos de ver material de la versión de consolas y cuanto de esto va a llegar a ellas... ![[angelito]](/images/smilies/nuevos/angelito.gif "angelito")
![[flipa]](/images/smilies/nuevos2/flipando.gif "flipando")
Jebi-Motors escribió:joder hay momentos que parece que es real la lechee
Also, there is another multibody solver in the works (not by me, so don't worry, not distracting from tire dev) for the chassis, that may also bring improvements you can feel.
So while I started doing more work in the "field" (on track) vs. in the "lab" (offline dev and analysis), I started playing around with a fifth carcass model. Up until recently I have had these four carcass models in my "lab":
* Pacejka (which is both carcass and tread holistically together - the stock Magic Formula)
* BrushCarcass, carcass portion of current Brush based model (actually has some strong similarity to RigidCarcass)
* RigidCarcass, which is not really "rigid" any more, but started that way, although it is not truly dynamic either. This is what is in the current STM that the devs are testing.
* ElementCarcass. The finite element style fully dynamic carcass.
This new carcass model, which I called FlexiCarcass, is a fast fully dynamic carcass. I started playing with the idea as soon as we raised the physics frequency (at which time I became concerned about the CPU budget for the real ElementCarcass because my rig at the time was not even keeping up well with the current physics overall on all builds). In very hand waavy fuzzy terms I'd guess that the FlexiCarcass gives about 70% of the value of the ElementCarcass for about 20% of the cost.
The reason the RigidCarcass is rolled out first is because is it very simple. So if testing shows any artifacts in STM overall it will be easier to isolate the defects. Once the system is stabilized around the RigidCarcass we can move to another carcass. The ElementCarcass can be downrezed to cost as little as the FlexiCarcass, but at that point it may not be adding as much value where we want it. The FlexiCarcass will likely give a lot more value at the lower budgets. However, the value of the ElementCarcass as more CPU is budgeted is much more open ended. So much so that eventually even the graphical tire deformations on screen could come directly from the ElementCarcass carcass model.
One rather large upside of the FlexiCarcass over the RigidCarcass is that we'll get the value of sampling forces at the hub instead of at the patch*. So we should be able to feel much more of the tire carcass dynamics through the FFB (vibrations, damping, etc) than we do now.
Someone posted something about when the STM model does hit WMD that that will be the final major qualitative jump for pCARS, and that people can start making their final physics judgments then. This is not true. That is why I posted that we already have 5** carcass models in the lab. There is plenty of ground for improvements that may have real impact even after an initial STM release. Also, there is another multibody solver in the works (not by me, so don't worry, not distracting from tire dev) for the chassis, that may also bring improvements you can feel.
( BTW, I chose the term seta from the feet of geckos. In the model a seta is analogous to a bristle in a bristle tire model, but the math model and the integration is different than what "bristle" typically means. All those other seta meanings are cool too though. I especially like the silk one)
* technically, we can sample at the hub for RigidCarcass too, but that is just a straight transform, so in the end it feels no different than sampling the patch once someone dials in their personal transforms (FFB parameters they like).
** Actually, there is a sixth model that I have not tested yet, but mostly implemented, which is a traditional String model. I do not really see how the String model would be any better than the FlexiCarcass in any aspect though, so I don't see myself worrying much more about the String any time soon.
![[looco]](/images/smilies/nuevos2/borracho.gif "loco")
Rivroner escribió:Si es que esos reflejos, luces y la lluvia no los he visto nunca en juego alguno de coches la verdad.
![[tadoramo]](/images/smilies/adora.gif "Adorando")
denis74 escribió:Bueno veo que currololo os ha puesto al día con ese notición de Nurburgring GP en Project CARS. La verdad es que lo tienen practicamente terminados con detalles y demás. Solo falta añadirlo y a correr. Ahora vamos con unas imágenes que han colgado:
![[Ooooo]](/images/smilies/nuevos/sorprendido_ani1.gif "Oooooo")
![[plas]](/images/smilies/aplauso.gif "Aplausos")
Here's some very early previz - not much about animations, but mostly choreography and camera tests. Currently we are focusing on 1st person camera mainly - as soon as you would enter pit stop, camera would switch into first person, car would be driven to garage automatically by game and player should make decisions about tyres, amount of fuel, repairs and such things meanwhile ... those decisions will affect how long pit stop will take (more fuel, repairs etc. will take longer).
as the first step for animations, it was necessary to coordinate pitcrew choreography to make sure they can move effectively as in real, without crossing each other paths and also to cover various vehicles with different fuel intake and air jack position. For simplification, we will make air jack for all GT cars (for now), even for those which wouldn't have it in real ... it's a game after all and we want to finish it one day, so we have to use any possible shortcut at this stage . However once it will be all done, we can go into much more depth and get even closer to real ....
EDIT: Picture with fuel intakes contains random cars from our bank of existing vehicles. Representing just group of cars with intakes/airjacks at those positions. It's not certain vehicle model we will have in this game.
![[babas]](/images/smilies/babas.gif "Babeando")
