Jump to content

bn880

Members
  • Content Count

    530
  • Joined

  • Last visited

Everything posted by bn880

  1. bn880

    1.10 and analog Handbrake

    Most likely the 50% analog range possible now is considered enough by them... but man, if they release future seasons/content in 2020, maybe they should reconsider this (and TBH also the clutch nanny). These are the basic/core aspects of the game/sim. The driving bits.
  2. This is the problem with most people who make assumptions based on feel and not facts. "For sure i can go 7s faster on PC" , "For sure that cut was 10s".... check yourself before you wreck yourself as a wise man once said . 😛
  3. There is no reason to break things up per platform other than a technical limitation. (possibly legal/financial as well) The point is that it doesn't make sense from customers' / competitors' perspective. Edit: But yes, if you HAVE to break it up, have separate eSports programmes for each then. Separate champions. (this would make more sense anyway)
  4. I agree this is a bit messed up, but more messed up was that degradation level was not announced to the competitors (and other conditions), there was no practice mode once you entered the qualifier for warmup, no setups, of course the cuts, but also a few people had issues where their times didn't upload and they were cut or that they couldn't even connect. Not to mention that one car class should be used for an esports event in rallying so that you don't have to learn every single class to compete. Maybe 2. On top of this the detailed end times of each qualifier were not announced along with the dates.
  5. Way too much blueish fog/haze/smog in Finland (all the videos uploaded) for some reason. Here is the still video pic from the Codies blog for Finland which looks GOOD: And here is the reality in the game, and the fog seems to be there all the time for some reason: The same problem exists in Germany. Can we please have clear vision at a distance in both events?
  6. Things that I would like to see improved, most of which caught me out even personally: 1. If you do one shot time trial entries like this year, you need to give people the exact stage conditions, and an ability to practice them. So it would be best if practice would be inside the World Series tab with exact stage setup. For example some stages had medium deg, some had high, in R2 that meant I didn't practice high deg which can be 5-8s faster (but instead took a rut off the stage). 2. The time of opening and closing of the qualifiers should be posted online! Not just dates, the exact GMT times. Having a countdown hidden inside WC sub tabs is not enough, most people are too afraid to click there as it may require qualifying. 3. Actually the leaderboard times should not be visible for qualifiers until it's done. So that people with busier schedules etc can qualify earlier and not have others chase them down. 4. Would be better to select a class of car to do the competition in, like R5 or R2 etc. Basically - The current world series was too disorganized for me to qualify. I now know I had pace in hand in the R2 event if I had practiced on High Degradation like some people who found out it was high not med, so congratulations on screwing that up. 👎
  7. Hi, if you mean importing the video into Motec itself, you can select "Show Video Controls" in MoTeC for the video stream (right click on the video window). Pause everything, press the little lock button to unlock sync options, and just zoom in on your data to detect when "Running Lap Time" starts to tick up, set the MoTeC cursor there. Then drag the video cursor as well to the time when your car started moving in the video. And press the Lock icon again on the video to lock them together. MoTeC can be a little buggy with video playback at times, and not all format display. If you mess around with it you will get it though.
  8. 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 until further notice. This is due to Microsoft improperly describing their Universal Runtime to developers.
  9. To be honest this doesn't seem related to performance. I think the fog/haze actually adds processing overhead more than anything else. It's mostly just a few of the lighting options that are doing this.
  10. @Cortextual over to you to clarify if you wish
  11. Conditions: "Mid Day Forest Fire"
  12. If you are on PC You can use https://www.racedepartment.com/downloads/racetrack-data-acquisition-rda.26829/ And analyze the logs in MoTeC. there you can see if slow/fast bump is making a difference if you repeat your tests.
  13. Yes this is obviously a compromise and workaround, not a fix. They should basically make it clear with all the options maxed out.
  14. It seems that turning off some of the advanced graphics settings near the bottom, especially bloom etc reduces the haze effect significantly. For example here are pictures I have from Germany (as I don't have Fin yet), with Ultra everything, and then Low/Off almost everything. Ultra Low Plus turning off TAA can help this a lot as well, I just haven't done it in the screenshots. (I keep it on as I like to remove some of the pixelation) Anyway, hope this helps some with Finland as well.
  15. bn880

    More realistic gearbox simulation

    Yes absolutely this is true. But by the way, if you enable "clutch override" assist, you can clutch kick. But I agree that A) Sequential cars are shifting too slow and costing you time. B) dogboxes should be shiftable without clutch and C) that you should have a mode without automatic clutch help (clutch nanny, another thread is already present for this)
  16. @richie if you stop he will stop now too. (it's a reaction to comments you made earlier) I just want the game to be fixed as there is no way I am going to buy this DLC ever if it stays like this. And I can't recommend it to anyone I know as is.
  17. @richie now is seriously a good time to stop trolling. Because that's all you are doing. You've said you prefer it this way, but most people don't and it's not usual/realistic for the location, so please try and act like a grownup.
  18. Maybe that's true, I don't really play RX currently so I can't relate and comment on that. (it's a bit of a different topic to the Finland Stage Rally haze topic though for sure 🙂 )
  19. Okay, well extremely unrealistic is true. Visibility most of the time there is like 40Km. Tragic relating to the implementation of fog strictly, and in terms of someone sitting there and adding this much fog IMO it's a tragically bad decision and shows some lack of visual QA. Someone should have said "hey, I can't really see at 200m in Finland during mid day, please fix this"
  20. Got anything better to say, like contrary evidence?
  21. If your observation skills are weak don't blame others. You have been presented the evidence several times in the form of photos. There is not much else to say, its extremely unrealistic, very obvious, and that's that.
  22. Fog in the game COULD be cool, it it's not currently. The current implementation is tragic.
  23. 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.
  24. The reported speeds are a bit off BTW. (faster than they were during the crash)
×