Does CrewChief work with F1-2018 on PS4??
Printable View
Does CrewChief work with F1-2018 on PS4??
I do not think it does.
I didn’t think so :( That’s a shame.
Should be SO useful in that game as a when you drive in cockpit mode you can’t see your wing mirrors unless you want to look like you’re sitting in the rear wing.
i did look at the UDP data format for F1 2018, and it's very complete - the developers have done a great job there. However, i don't have the game and it doesn't work in VR so I can't really play it anyway (my wheel is attached to my VR rig). This means I'd be developing the app 'blind', assuming that the UDP data is exactly as it appears and works exactly as described. This is rarely the case - it takes a lot of time to work around all the quirks and unexpected behaviours for each game.
Having said that, i've wired up the basic stream reading using longtomjr's UDP client mapping stuff here: https://github.com/RacingSimTools/F1UdpNet
I've had to change the way the app reads the data a bit and i'm unable to test it but it's a start
Cheers for getting back to me Mr Belowski. It IS surprising that they haven’t included VR support in this years game.
I’m happy and appreciate that you’re thinking about it and trying to figure out how to make it work with F1 2018.
I’m happy to help out with any testing or anything need however I’m on PS4 not PC. You got back to me on another thread about trying out a few things to get CrewChief working on my laptop for Project Cars 2 on my PS4. I got home too late tonight, I’ll give it a shot tomorrow and let you know how it goes????
i've wired up a basic F1 2018 spotter implementation, but this is based on several assumptions about how the game's UDP data works. If all of these assumptions are correct then the spotter should work. If some are not correct then it might do nothing at all, or give seemingly random calls because it's rotating the opponents' world co-ordinates incorrectly (because the app's not interpreting the player rotation data correctly). So it's a bit of a long shot. Of course, this also depends on your network allowing the UDP traffic between the game and the app.
Still, it would help me if someone would give this beta a try and report what happens:
http://crewchief.isnais.de/CrewChiefV4.9.5.1.msi
Done, I’ll give it a shot. If it doesn’t work on my Laptop due to whatever network/communication issues I’m having there, I’ll try it on my Samsung Tablet which is where I’ve been using CC for the last 6months with Project Cars 2.
I’ll let you know how it goes ????
Hey, first off - Thanks for doing this!
I just recently heard of this tool and was wondering if it works with F1 2018. So I downloaded your beta and tried it. (default config, first installment)
F1 2018 has two UDP formats: "2018" and "Legacy". With "2018" I get a lot of these: "Error reading UDP data Index was outside the bounds of the array." and obviously the spotter does not work. The "Legacy" option does not throw any logs or errors, however I got no response from the spotter while testing.
I only tried Grand Prix Mode in FP1 while dangling with the AI, but no spotting happened.
12:55:15.726 : Using game definition F1 2018 (spotter only)
12:55:15.761 : Loading default command macros from installation folder
12:55:15.765 : Loaded 94 default car class definitions and 0 user defined car class definitions
12:55:15.780 : No user defined landmarks found
12:55:15.789 : Starting queue monitor
12:55:16.797 : Monitor starting
12:55:16.812 : Polling for shared data every 100ms
12:55:16.821 : Initialising...
12:55:16.824 : Listening for UDP data on port 20777
12:55:26.219 : Error reading UDP data Index was outside the bounds of the array.
12:55:26.235 : Error reading UDP data Index was outside the bounds of the array.
12:55:26.274 : Error reading UDP data Index was outside the bounds of the array.
...
yes, i screwed up that beta - I fixed the code yesterday but haven't updated the installer yet. Just a minute, i'll do it now and add a link...
here you go:
http://crewchief.isnais.de/CrewChiefV4.9.5.1.msi
As I said previously, i don't have the game so this is all a combination of guesswork and interpreting the UDP format specification, and (as you've already seen) it's entirely untested. But I'd really appreciate some feedback
Errors are gone, however still no spotting happening.
Any way to give you a more detailed log?
yes, if you create a short cut to the app's .exe file (default location is C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4) and edit the target to add DEBUG to the end, so it looks like this:
"C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4\CrewChiefV4.exe" DEBUG
then run the app from that shortcut, a new checkbox will be added to the app in the top left corner, called 'Record'. Enable this and start the app, then start a session and play for a couple of minutes. When you stop the app, it'll dump all the collected game data to a file in My Documents/CrewChiefV4/debug_logs
If you could ping that over to me it will be very helpful
Just wondering if there is any progress on this? Only just discovered this forum and had no idea that F1 2018 was being look at for this great app. I race on the Xbox and run the app on my phone so if there's anything available for that I am more than happy to be a guinea pig for you. I have done similar for the dev of rsDash as well.
Cheers
There just isn't much call for an F1 2018 implementation. The app does have spotter-only support for F1 2018 but there are some issues with the UDP data and it's a huge amount of work to implement, and it would be unlikely to beat the build in engineer
Ah ok, many thanks for the swift response :)Quote:
Originally Posted by mr_belowski
Hey, its been a while on this thread but i've managed to get Crew Chief to work on console(xbone) for F1 2018, you need to use SimHub as well but its doable.Quote:
Originally Posted by Hammerpgh
Excellent stuff. Many thanks i'll get on this. I'll have to look at this SimHub as well as I don't have that.Quote:
Originally Posted by Zero1273