Jump to content Jump to content

NinjaElmo

Members
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

21 Unleaded

Gaming Setup

  • Platforms
    Steam
  • Peripherals
    Controller

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah Singapore is a funny one. The data I've looked at shows it as a track that the AI is slower on, and I've seen it brought up often on the forums and by various Youtubers as one of the AI's worst tracks, but then lots of people go crazy at the thought of making a 'difficult' track even more difficult. It's a punishing track sure, but the AI seems to be pretty slow there.
  2. Hey all, Thanks to everyone who has left feedback, particularly those that covered all the tracks and used the calculator properly. Unfortunately I had to exclude a few results from people that didn't seem to set the calculator up properly (if your AI is too fast/slow at Spain, the whole calculator will not function correctly). It looks like lots of people have been using this calculator daily, so I feel like I have a bit of a resposnsibility to make the recommendations accurate. I've updated the calculator following the v1.12 update. Changes listed below: - Used top 10% time tr
  3. Fixed, sorry about that, it should be unlocked now. You should now also be able to copy it and have it update properly too. I'll aim for an update with more accurate suggestions once the performance update comes out.
  4. Yep, were definitely on the same page about why we can't trust our own track performance/opinions. Unfortunately a perfectly consistent across all tracks person doesn't exist 😞 I was hoping with enough feedback on my survey I could essentially average things out, so essentially average out everyone's track inconsistencies, but I haven't got enough responses to get a clear picture. Seems like people are just using the calculator straight up and taking it as gospel that it will make every single track a competitive race for them. I took down the youtuber Tom97's hotlap times in the hope he
  5. @Gonira Oh boy that would have taken a long time, I salute the boring and hard work. I plugged those times into my calculator to see how they affected the numbers. Dealing with the numbers is a mess, so you'll have to bear with my observations on the results so far: - Using averages instead of world records made some of the recommendations closer to yours (n=8), some further away from yours (n=7), and some had negligible change (n=5). Austria came equal to yours, but from first hand experience, my calculator feedback, and general complaints I've seen on these forums, a +1 for
  6. From what I could tell, the difficulty jump starts after 105. 95 - 105 difficulty was around -1 second per lap, but 105 - 110 was also -1 second per lap. My Team mode definitely has a lot of problems for CM to fix before players can get a consistent and challenging season without making changes and self-imposing rules.
  7. @MilligramSmile For now, I suggest only changing the difficulty of the following tracks: Bahrain -5, China +2, Austria +3, Britain -7, Belgium -4, Russia -3, Singapore +5 Japan -3. That's based on areas that my and Gonira's findings agree. Other tracks leave at your base difficulty. For the strict corner cutting conversation - basically some tracks can be much easier if the player cuts corners, because the AI never cuts corners. The last chicane on Canada is a great example, where a player can blast through on lenient corner cutting settings and reduce their lap times by 0.5s, whereas so
  8. Also Canada in your results could possibly cause issues, but it could be down to that last chicane. In my calculator it's a +0 track, but all the feedback I have recieved on my calculator has been that that's too slow (2x much too slow, 2x too slow, 1x accurate). (As a side note: Austria on my calculator is a +4, but the feedback I have recieved is that it's still too slow (4x much too slow, 1x too slow). Let me know how Canada goes on strict settings with your recommendations though, people might just be flying over that last chicane and then complaining that the AI is too slow. For comp
  9. @Gonira Interesting stuff, it looks like we had similar methods. My calculator is pretty much doing a similar thing, just mathematically instead. How did you get the top 10% times? It looks like it will take a LONG time to scroll down that far in the time trial leaderboards...I am interested in trying the average times for my calculator and seeing what results it spits out. If you've got the times on a sheet, can you send them my way? Off the bat it looks like your Austria suggestion could cause issues, the AI seems particularly slow around here, even with strict corner cutting. I agree w
  10. I got confused by this too when I started, it's not very well designed. It should really just be a coloured box below the name, not a coloured underline.
  11. I had this on a Dry - Wet - Dry - Wet 100% race at Singapore. On the second wet session, they pitted for dry tyres, then for inters the next lap. Granted I pitted for what I thought was my final set a few minutes before the second rain session hit, I had Jeff on silent so didn't realise I there would be more rain coming.
  12. Possibly this question is the one you were thinking of? I do remember a discussion about this too, but don't recall their being a definitive answer. That whole thread is helpful for working out some of the finer details in how the game works. As a side note, check out the RealSport F1 2020 Setups, specifically the ones by Jacob Hancox. I race on 100% distance, ~85 difficulty, and I've been finding the setups from that site super helpful in terms of making a good race setup and explaining the steps behind each change. The game could do a lot more in terms of explaining and showing setup ef
  13. Yeah, I agree with you @marioho, it's probably somewhere inbetween to make things less resource intensive, and for the most part, it does a good job. Changing conditions and certain tracks do seem to cause issues, but then of course that is always going to be the case, since some people are gods at wet weather conditions or Monacco. In terms of the telemetry output, basically I think it's done to make the lives easier for telemetry program developers. The game outputs setup data for all drivers, regardless of how many and whether they are AI or not. Telemetry developers just need to read
  14. Haha all good, I didn't take any offence, just thought I needed to point out my perspective and why I don't think changing telemetry program will have different results. It is definitely a weird, and as you pointed out, deliberate, choice for CM to make. My guess is that the AI 'setup' has zero impact on how they actually drive, but because of the way CM has designed their telemetry output, each participant needs to have a 'setup', so those are just the values CM has given to any driver that is AI. If there wasn't the big AI performance issues on some tracks that you pointed out, it would
  15. I was messing around with reading F1 2020 telemetry in Python, it's all entirely my own code. I can assure you that I'm not defaulting anything in my program (I would get an error if there was no value), and that according to the F1 2020 UDP specification post, the packets are sending that setup info for each participant (so each AI and the player). There is the potential that the game is defaulting that information when it sends it, which would cause all telemetry programs to show the same result. Given this post seems to say that the AI doesn't change setup, I would think it's just the
×
×
  • Create New...