Crew Chief Beta

Unfortunatelly this is not possible because of the incompatible interface structure.

 

I wouldn't say it's impossible, but I understand it requires time/resources/money.

 

And a rewrite of the underlying code unfortunately. It's square pegs and round holes folks.

If anything we might end with a more advanced native spotter in ACC as CC seems such a postive addition with players.

 

Same here

It is THE positive addition for me!

I'll stop updating CC to keep it working

 

Changing an interface is one of the worst things you can do in software development. Usually this is forbidden. An interface must never be changed, the only possibility is to overload it.
So neither Kunos nor Jim will do changes.

 

With this approach you would have only interface 1.0. There is always possibility to change, especially here where there is so little information available to outside world. And to be honest I don't think it's "interface issue" because you could always develop a proxy - it's rather lack of information or correct timing from ACC (check Jim Britton post).

I'm just saying I would be more than happy to pay for either DLC (e.g. integrated CC) or external application. But it's up to Kunos to decide if this is worth their time and resources. I guess they have higher priority issues at the moment.

 

It works, but is not as good, its more lull. Its very clear who copied the diea from whom here. CrewChief's spotters are more ... they are more - I mean they are - you see...? Spicey.

Also, I did not test ACC spotters long before switching them off in favour of CC, but they led me into two collisions, claimng a conflict was resolved, and it wasn't. I prefer CC's spotters every time!

 

Fully OK with your statement .... If I listened to the ACC spotter ... "free on the right" yesterday at Bathurst .... I should have bumped the car at the right .... its rear back was still at the right of the front of my car..... in the first long straight

 

Is there some documentation about the shared memory API that ACC delivers and the layout that CC expects? I develop this kind of stuff for a living and would be happy to chip in if it looks feasible...

 

Please check Jim Britton post from CC. We all know how to do it, but there is a lack of data/timing from ACC.

 

If you are referring to the post I think you are referring to, I think I read it.
What I got was that CC expects a snapshot of the gamestate at a single point in time, and that ACC was updating different variables at different rates. Some other data has to be collected over UDP. I would create a plugin/daemon that gathers the output of ACC (shm and UDP) and then create/interpolate that data at a particular point in time and export that to a shared memory snapshot that CC can read.

 

I've absolutely no clue what you're talking about but I'd do basically exactly this too.

Thanks to you for offering help

 

He means that he builds a bridge that collects the data from ACC, converts it to the format CC expects and inter-/extrapolates data at a certain point CC expects if they should be not available at this point of time.

 

Exactly. I think ACC + CC is the best of both worlds. The immersion in VR is unreal, even with the bugs. I would hate to see that go.

No promises though.

 

I think getting the interface description from Kunos and Jim should not be a problem.
Just contact them and you will see if they can/will/want provide you the required documentation.

Hope with your help CC can support ACC in future iterations.

 

I'm sorry guys. I was just joking around a bit
Beside the fact I've no clue how to create some kind of "ACC-CC translator" I understand the intention behind the tool.
I'd love someone can make it work.
And like @Dimitri Staessens said it is the best of both worlds and the immersion CC is able to add is unreal. Even in this unfinished state.

 

Hi Jim,
Really sad to see CC leave ACC. I find it the essential app and really adds a level of immersion. It wouldn't be a proper race without sweary Jim expressing his disappointment in me. I think like others, I'll just stick with the current version to retain the ACC support. I can live with some of the info being incorrect/out of sync.

I do however feel your pain. I've been working with shared memory and have been caught out a few times by synchronisation issues and I've got challenges ahead on how to plug the gaps in information. This isn't Kunos' fault, but just me tried to use the APIs for something they weren't intended for and I guess you have the same problem.

Thanks for all your efforts
Doug
ACC Results Companion
https://www.racedepartment.com/downloads/acc-results-companion.28298/

 

Could you not Keep ACC as a functional part of CC, and just use a disclaimer whenever ACC is selected to state that there are issues with it and that it is no longer a supported module of CC. Maybe even have it in a separate menu. I also will not download the new version because although CC is not perfect in ACC I would MUCH rather have a less than perfect version of CC than no CC at all.

 

I am following the discussion, I do not understand very sincerely, but I say this .. I would be, like others, willing to pay to have a complete and functioning CC, so I can provide my support.

 

I appreciate the radio compliments from Jim on making a good pass - that seems to work well. Items that work: when others are pitting, spotter, commentary on performance ("nice pass", etc.), time of last lap, gaining/losing time, of course using your name (or name you've selected from the list). Not sure if it makes sense to offer a "lite" version, but it would be "robust" compared to what the ACC in-game offering has. I get that not being able to offer all of the functionality seems like an incomplete offering, but as an alternative the working functions are still better than the in-game.