So are we all happy this this is now stable and represents the final version for the upcoming patch? I'm a lazy lazy man and the prospect of doing *any* work brings me out in a cold sweat so the risk of having to do work twice makes me absolutely crap meself. I think I might know the answer in advance, but any idea when these changes will go live?
looking at the recent changes, one thing might trip up my app - the SessionPhase enum used to be public enum SessionPhase { Unavailable = -1, Garage = 0, Gridwalk = 2, Formation = 3, Countdown = 4, Green = 5, Checkered = 6, Terminated = 7 // seems to be 7 when the session is 'killed', it isn't in the API but does happen from time to time } Now it's public enum SessionPhase { Unavailable = -1, Garage = 1, Gridwalk = 2, Formation = 3, Countdown = 4, Green = 5, Checkered = 6, Terminated = 7 // seems to be 7 when the session is 'killed', it isn't in the API but does happen from time to time } Garage has changed from 0 to 1, with 0 now being the undefined value. Obviously my app will work with the new enum values but I was wondering if this was a typo? I'll add some logging so the app will grumble if this value is 0
Hi, Garage = 1 is correct. It's been like that since july 2015. 0 is phase start. Used temporary after joining/switching session. 7 is phase end which means the session is over.
http://crewchief.isnais.de/CrewChiefV4_for_r3e_beta.msi This is a version of Crew Chief that uses the struct as defined in the october patch branch. It's only for r3e beta testing - it (obviously) won't work with the regular version of the game. Give me a shout if it doesn't work or trashes your house
I was going to offer my services as a beta tester too but you're expected to actually put some effort in, and test rather than just play. The "making an effort" part disqualified me
Yeah, that's exactly why I never applied too...but maybe 3rd party "devs" should be allowed just to make sure that their shit works
There, fixed that for you It would be cool to be able to access the new stuff but the shared memory changes are quite infrequent so it would feel like we're taking the p!ss a bit having beta access just in case, but not having to do any proper beta testing
I think you could both apply to be beta tester in this game, you already did enougth here to proove the value of your inputs The guys from SimXperience are in too, and I don't think they do much that working on their own stuff for compatibility purpose
@Viktor Öfjäll I'm trying to update the classes to the latest October update and saw this in the C# example Shouldn't the C# PitStopStatus property be enum PitStopStatus instead of Int32 ? Thanks!!!
Well my Crew Chief didn't spit me in the face like he normally does, so.... yeah, big improvement. Only had two short races but didn't experience anything out of the ordinary and as far as I can tell everything that should have been there was there. If I find more time I'll do some more runs and pay attention to the details. Just one thing I've been missing in the public release as well lately, I don't seem to hear the background sounds anymore, my fault? Come to think of it, nvm answering that question. Let me re-phrase: Anything I can do get them back?
dunno, i guess it depends on what you did to make them go away Turn them up maybe? If I remember correctly, the background sounds are played using a Windows media player object, so maybe you killed media player?
I kept the enums as Int32's since the current master branch example does that (probably to explicit show that they take up 4 bytes each, and memory alignment is very important). Using the enum should work though since it should be the same size as an int32 by default. Added a comment to see the PitStopStatus enum to the c# example.