bn880

03.07.2020: Version 1.6 is out. New: Support added for DR 2.0 Scotland stages. Fixed issue with logging not working for some users. Moved “Reset Best Lap” menu item below all others to avoid accidental selection. RaceDepartment Link in first post

03.07.2020: Version 1.6 is out. New: Support added for DR 2.0 Scotland stages. Fixed issue with logging not working for some users. Moved “Reset Best Lap” menu item below all others to avoid accidental selection. 16.01.2020: Version 1.5.2 is out. New: Support added for all remaining RX cars for DR 2.0 released until this date. *Ford Fiesta Rallycross (STARD) recognized as Ford Fiesta RXS Evo 5. Support added for all remaining RX venues for DR 2.0 released until this date. Support added for BMW M2 Competition stage rally car. *Detected as Mitsubishi Lancer Evo VI Support added for DR 2.0 Greece stages. Support added for DR 2.0 Finland stages. Special thanks for V1.5 data gathering to: RSR SereneLogic 05.01.2020: Version 1.4 is out. New: Support added for DirtFish free roam. Support added for Peugeot 306 Maxi DLC car. Changed: RDA now saves each new stage attempt to a new file, allowing for much easier and cleaner tracking of fastest runs. Special Thanks: Special thanks to mrjiffy6, Malkael, Mike Dee and Cortextual for their contributions. 16.08.2019: Good news is good news. Version 1.3 of RDA has been published. New: Support added for DR 2.0 Wales Event Support added for all DR 2.0 v1.7 RX Venues Support added for all DR 2.0 v1.7 RX Vehicles (note “VW Polo R Supercar” is detected as the Audi Supercar) Support added for DR 2.0 Ford Focus RS Rally 2001 Fixed fastest lap timing display when swapping RX vehicles on same RX Event Planned: Support for Windows 7 and 8 is still planned. Special Thanks: Special thanks to Malkael for collecting the data required to make this update happen. Special thanks to Mike Dee and Cortextual for their previous contributions. 02.07.2019: Even More good news Everyone Version 1.2 of RDA has been published. New: Support added for DR 2.0 Sweden Rally Event (all Stage Rally Events from 1.51 now supported) Support added for Lancia 037 Evo 2, Porsche 911 SC RS Group B RWD Stage Rally cars (all Stage Rally Cars from 1.51 Supported) PDF now features a change-log at bottom Planned: Support for RX is still planned but not scheduled, donations would speed it up. Check Discord if you wish to help with collecting data for RX RDA support. Support for Windows 7 and 8 is still planned as well, but also not scheduled. https://www.racedepartment.com/downloads/racetrack-data-acquisition-rda.26829/update?update=48907 27.05.2019: Good news Everyone Version 1.1 of RDA has been published. New: Support added for all DR 2.0 v1.41 Rally cars including 2000cc. Support added for Monaco and Germany Rally Events. RDA now renders on top of game windows so you can use Live Performance over windowed/borderless DiRT Rally (2.0). Planned: Support for RX is still planned, but donations would speed it up. Check Discord if you wish to help with collecting data for RX RDA support. Support for Windows 7 and 8 is still planned as well. Download Version 1.1 https://www.racedepartment.com/downloads/racetrack-data-acquisition-rda.26829/ Hi all, my data logging tool that I should have released 2 months ago , has finally hit the shelves: https://www.racedepartment.com/downloads/racetrack-data-acquisition-rda.26829/ RDA Represents several weeks of full time software development which is released to you for free but with ability to donate if you find it useful and wish to support further enhancements. What is RDA? RDA is an application that can log telemetry from DiRT Rally (all stages/courses/vehicles) and DiRT Rally 2.0 (base release Cars/Stages and may work for DLC stages) to CSV, BIN, or MoTeC LD files. RDA also allows you to compare instantaneous and live Delta T and Delta V if you have already completed a stage/lap in the same vehicle. Your best stage/lap is saved on completion. Currently the live deltas are rendered only on a secondary monitor or beside the game windowed. Sample Videos ALL THE INFORMATION BELOW AND MORE IS AVAILABLE INSIDE THE PACKAGED PDF WHICH INCLUDES AN EULA Key Performance and Features RDA is very light weight; written in C++17 (importantly not Java or scripts) and does not utilize any extensive libraries such as boost, .NET, QT/wx and other UI libs to keep the data logging and loading performance impact completely negligible. You should not notice even a 0.1FPS drop when logging. In addition to using minimalist C++17, the application logs LD data to a temporary BIN file format instead of text/XML for ultimate performance and data safety in case of a system crash. (Recovering such data from BIN to LD currently can only be performed by the author “bn880” due to possible licensing issues.) Data and Frequency Precision RDA uses a comprehensive algorithm to save LD logs in maximum precision for all data channels without significant processing overhead. This is unlike any previous LD file data logger for other simulations. The frequency of the channels is also precisely calculated and saved based on an extrapolation algorithm and full passes of the collected data points. It is however crucial that you log at less than the full sim render FPS (about 80% or less of the FPS) or that your render FPS remains constant with Vsync if you want to have precise timing in logs. See PDF for more features... Quick Start / Installation Extract zip Extract the ZIP package into a folder where you have full privileges (read/write/full control), usually this simply means NOT in ProgramFiles (x86). Setup DiRT Rally UDP Set up DiRT Rally UDP output to your desired unique RDA port as per the How to set up DiRT Rally and DiRT Rally 2.0 UDP ports section. (inside PDF in package) Run RDA Run ./RDA/RaceTrack Data Acquisition.exe alongside your game to capture data logs and to view live Deltas once you complete a lap/stage once. (you can make yourself a shortcut to the exe for future use) Live Delta viewing is shown on the RDA main panel, and requires a secondary monitor or running the game in windowed mode with RDA visible on the same monitor. See Delta T and Delta V display. *** NOTE *** If you try to use RDA to log cars OR stages/tracks that are not supported no files will be generated, there will be no deltas shown, and you will need to restart RDA to resume logging. When data logging is working and live recording a stage/lap the Record button turns red. See Figure 6 RECORD and STOP (+SAVE) Button states. (inside PDF) You can find your logs with the File>Open Log Folder file menu entry. Install MoTeC i2 Pro v1.0.21.30 (not included in this package, you need to get it yourself) In MoTeC i2 Pro go to "File">"Project">"Open Project..." and open the supplied project: <RDA Install dir>\MoTeC Projects\DiRT Rally\Project.mtcprj Open Log File in MoTeC Pro You can now open your recorded LD log file in MoTeC. As of version 1.0 detailed GPS track maps (inner/drive/outer lines) are provided for Fourketa Kourva and Waldabstieg from DR. However you can generate these GPS maps in about 15-30 minutes with the correct procedure, and any stage you have driven will always be visible as a drive line with heading anyway. See Track / stage map generation procedure. Final Notes/Discord Enjoy, and remember to join Discord https://discord.gg/GKhwAcN if you have questions/comments/suggestions, and that you can Paypal bn880@hotmail.com if you wish to support further feature enhancements. (shameless plug) NOTICE: RDA will not work in Windows 7 or 8.1. This is due to Microsoft improperly describing their Universal Runtime to developers and omitting certain features from CRT for Win7. 16h of development would need to be funded by donations to cover conversion to C++13.

Work on making the softs last, but yeah, still use softs and do your best, will be faster. If you just wanted to be safe you would have to go with hards , but it would cost you a lot!

It's not about a consensus. All the guys at the top as far as I am aware were using softs because they out perform the mediums and degrade at just very very slightly earlier than the mediums (to worn level). (The top 0.1% decide here, who are a very small minority) Overall the softs were faster on those 4 stages if you drove at near WR pace. The tyre tests that people have done on the forum here were not accurate to what was happening when testing the tyres in the wales stages. (most likely inconsistent drivers, not using data analysis to check themselves either)

Probably many, however softs may not have been a bad choice. 🤔

My SS12, just trying to get to the end to keep my position in the championship Which ended up being a surprising P7 I really lost some pace after SS2 where I had a very unexpected moment pretty much on a line that I always take, which shot me into a log pile and over it, off the track. My car nor I were not the same after 😄 Also the degradation in SS12 was a bit of a shocker, hence why I also eased off another ~10s there. It was a very tough Cup, busy time, unfamiliar events... so glad to at least get a great result from it. 🙂

^ Not bad for going in relatively cold to the stages without that many hours in DR2! Meanwhile I just finished, provisional P5 in wales, P7 likely and P8 in championship should be secure AW YISS! Really took it steady in SS12 ... had nothing to gain by pushing there 😉

Disappointing that P1 Championship prize has been expanded but nothing for the other spots. I guess the winner really does take it all.

Yea, I ended up 16th after 2 issues but still P8 in championship which could end in P9 to P7 easily in Wales My run of SS12 which was very good with P9 stage time: You can see a bad line at the end of the big fast downhill left (after fast section, near 50s) where it tightens, had to use extra road and hit some posts to open it instead. Should have had a wider entry there to open up the 3/4 left tightens. Otherwise it was quite good with just a wiggle on a landing 🙂 Love this competition, but together with also having other responsibilities, the 1 week events really beat me up physically 😄

My run in the final stage SS12 of New England, safe run as I had 1.8s to spare from my PB to move into 6th spot! Windshield damage is the standard clubs bug, I had no real damage after SS11

while the companies may try to look into this issue, in the meantime you need a friend to send you the missing nefs (make a backup when you get them as well). and it will start to work.

It was over before you got settled, commiserations.

There seems to be something very fishy with the results posted by @oliversolberg01 on twitter for the results in Greece where Oliver is listed in P10 for championship standings. https://gyazo.com/673813ad930e6f5553063939e34c71f8 The club results are here: https://dirtrally2.com/clubs/club/253326/standings/current https://gyazo.com/13db9dfd179395d21832f2c992bdecbc Where I am listed in P10. And here: https://gyazo.com/464c7cd4e3e87a7e48145f4208deaee7 Where Oliver is 67th Oliver only scored 778 points in Greece, meaning he basically retired. How can he still be in P10, he didn't win a single stage in Greece either? Here are the stage wins in Greece this week Last week's standings are here: Oliver was listed in 8th pos in the champ after Sweden, which matched the club: https://gyazo.com/4c3985a4ac8fb4cec034100d87ebcb90 So where is Oliver getting the extra 57 spots and 2600 points to be ahead of me? (he is now 67th in the Club after Greece) The Twitter post is clearly Fake News! (real fake news) @PJTierney

Just did 1.5 hours of career, was solid and fast (much faster than usual).

Server connectivity issues again..

I believe we only get 8 setup slots per car per surface type (gravel/tarmac/snow). Which is actually grossly insufficient. One should be able to save at least 2-3 setups per car, per venue. (wet, dry, WIP) It just makes it difficult to keep track of changes/setups as you would do in reality and would like to do in the game/sim. So how about just letting us save a very large number of setups, is there some reason why this is restricted, it's pretty much free in the code isn't it? Thanks.

This may not be seen as a bug, but I think it's severe enough to put here: The pacenotes in Scotland are quite problematic in practice, especially with faster cars. Here are the issues: Many calls to not cut or for tight corners come completely too late in faster cars. Many good cuts are not called, many "don't cut"s are not called either (for example for logs either on exits or inside open corners) Because the final lines with cuts are not considered for the corners they are often called way too severe.

Setups are not reset with the Reset RaceNet Data option (just tried it)

Do you recall if this also deletes tuning set ups? And does it by any chance delete World Records or times on leaderboards? (I mean the reset racenet data option)

Easy fix, no more exterior cams 😄 (okay side window visibility AFAIK is useful IRL in most instances except when the drivers cover the side windows with mud, so I generally agree with this)

I do recall Christina mentioned that they would check on the feedback provided and make changes as necessary. And well I guess the changes to be made were not significant when they saw the other things to fix. Don't think they were trying to deceive anyone. 🤗 Please remember also that there was a lot of indecision from the community on WHAT changes should be made, if any.

All this is common sense, the problem seems to be that Codies are mostly done with changes to DR 2.0. Hopefully they learned a LOT for DR 3.0 and what it needs (pacenote timing adjustments, editing and even recce are some of those things) Don't get me wrong, I still hope they offer some fixes if possible.

Version 1.5 has been released. Update Notes at top of first post.

This is mostly true, however for TimeTrial you need a system that discourages un-sensible cuts that is not risk based as that implies a chance you might get through fine. You do absolutely need something that is 100% guaranteed to cause trouble. like a penalty or slowing you down. So for the rest of the game I agree with you, but remember that TT people will take all risks until one out of every 50 runs they make it through.

There is not. We are suggesting it for DR 3.0 here: