Jump to content

Eagleizer

Members
  • Content Count

    69
  • Joined

  • Last visited

Community Reputation

12 New Car Smell

Gaming Setup

  • Platforms
    Steam
  • Peripherals
    Steering Wheel
    Keyboard
    Other
  • Steering Wheel
    G27

Recent Profile Visitors

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

  1. When large companies like Codemasters, Motorsport Gaming US LLC, Motorsport Network, Autosport.com, Motorsport.com and OTT racing television network, cooperate on an event that goes out on platforms that reaches more than 30.000.000 viewers every month, you kind of expect it to be a serious event. Knowing when updates usually happens have to be considered "special knowledge". It is also not correct that there is any regularity to this. There have been updates at very different times, at least in my part of the world. I have seen updates coming at midnight (my time) and in the afternoon, as it did for the 1.9 update. Even if I had such knowledge, it would be reasonable to expect that an update would be postponed for the sake of the seriousness of the World Series. There simply is no excuse for this, except being a terrible mistake based on miscommunication between the departments at Codemasters. Now they have to take responsibility and decide how to correct the mistake. I have a couple of ideas, but first of all, Codemasters have to comment on this and acknowledge the mistake like any serious organizer. Not that is really matters, but I don't consider half hour to be "last minute". You can't expect qualifiers who are participating in a seemingly serious global event to have detailed knowledge about when game is updated and what consequences it would have. In any serious event, any sport, the time available is the time available. That's it. There is no point in communicating imaginary limits that arrived before the expired time. And so what if it was last minute. It's in the words. Last minute is still within the expire time, so it does not add a liable excuse for Codemasters, or blame on participants who did not get a chance to do their run. The only reason I did not get to do my qualification run, is because Codemasters pushed their update. There are no other reason or blame to be made. Codemasters have full control of when they are running the event, when they decide to update, and what consequences one will have over the other. There is a timer on the events that tells you when it expires. The purpose of the timer seems clear. A planned update is not an unforeseen event, and they only had to wait for another half hour before pushing the update. Since there are no other events in the World Series the following week, there was plenty of time to do this update without interfering with the World Series qualifications. For something that is being advertised as "Planned for 6 months", you would expect that you could trust when you can actually do your run. About half hour before it expired was the perfect time for me. Since it's of interest, here are the most important reasons for doing my run "late": 1. Late afternoon is the time of day that we are least likely to have a power outage. 2. I do the main part of my practice when I can do that undisturbed, which is night and work hours. 3. Point 2 affects my sleeping habits, and therefore also the optimal time of day to do the run. 4. I had planned to do my run the day before, just as I did in Kopina, as it is raining season here, and thunderstorms always leads to short power losses, so it's a good idea to not risk having to drive then. Having a 24 hour buffer is plenty in this regard as it never lasts that long. So I was already "anticipating unforeseen events". But I was not feeling well the day before, and my times was fluctuating a lot, and it was definitely not the time to do my run. In fact, I was feeling sick all day up until a couple of hours before the event expired, and was already worried I would not be able to do my run. I had half hour sleep and did about 1 hour warm up, and that was that... According to the countdown timer, I still had a half hour to do my qualifier, so there was still time to do 3 more warm up runs. There are several other reasons for why I chose to drive when I did, and the most important after taking the above into account, was to be "in the zone". My timing for doing the Qualifier was perfect, as I was doing 7:10.xxx over and over, and did 07:09.970 on my last run before going to qualify. That is more than 3 second faster than the top Qualifier time. I don't see how participants are to blame for not driving earlier than the expire time given. The announced event was not finished. Simple as that. The update and the consequences of updating is not "circumstances outside organizers direct and reasonable control" as mentioned in the Terms and Conditions, and certainly not something that participants should anticipate. All this of course comes on top of previous issues. I came in second at Kopina. Lost at least 1 second in the first sector due to totally different track conditions than announced. I have never done any degraded track conditions, as I only do Time Trial, and seeing the track sinking into the ground in front of the car, and having the car move in a different way totally caught me off guard. (Don't believe me? Check the dates in my Achievement Progress in my Steam Profile. I did my first one 30. Sept., well, besides the surprise one in Kopina.) I then skipped Argentina since my old eyes cannot cope with the bobbing there, so although I wanted to fight for the total time for the 3 locations, there was simply no way I could drive there. I therefore put all my energy into getting a top time at Te Awanga, and have been practising there all day long for 14 days. Cheers :)
  2. Eagleizer

    DiRT Rally 2.0 World Series

    What the hell?! Did not get the chance to do the qualifier because you updated the game? What on earth are you people thinking? Just made the fastest time in practice and was going to do the Qualifier. I restart the game since there was no connection with RaceNet, and then it start downloading an update.. You need to fix this in some way so we can do our qualification. I have spent far beyond 100 hours practicing this stage for this.
  3. This is outrageous! I practice for 2 weeks, and when I restart the game to do the Qualifiers, the game is updating?
  4. Eagleizer

    Track Limits in DiRT World Series

    It's always a good idea to read the rules before calling fellow gamers for cheaters. (Calling other forum members for cheaters could get you banned) From the Sporting Regulations for the World Series (As IRL, organizers decide rules for the event.): 50. Drivers must obey track limits. Track limits are defined automatically by DiRT Rally 2.0 but exploits may be monitored by the Race Director or their assistant. Penalties and warnings will be applied as per the “PENALTIES” section of the rulebook. (Exploits in the gaming industry is referring to manipulation or taking advantage of "holes in the coding". Driving along track reset-lines, not being where you want it, is not an exploit in this regard.) 55. Time Penalty – The game may issue a time penalty for various reasons, including cutting corners and car resets. And an explanation of the above: Also don't forget that DiRT Rally 2.0 is a game with many unrealistic details you would not find IRL. Making limits that resembles ILR without moving the reset lines is an impossible task to implement. How are you going to control how much people are cutting, and what should be OK and NOT? If cutting should be limited in some places, it would have to be in the rules (Road Book) for the local event so the drivers are aware about where to cut and not, and how much. There are no global rule for this IRL either, as it is handled and decided by local organizers. Organizers in this case are Codemasters, and they have decided the rules and written them for you to read in the Sporting Regulations. You cannot just come here and decide that you are the one who make the rules, and what you don't like is cheating. Your comment on CRsedmicky's video is rude and totally out of place. He followed the rules, ergo, not cheating... He also clearly states that he does not like the cuts, (like all of us) but he did not make the rules. If you don't like the rules, complain to Codemasters. Flaming and harassing other players because you disagree with the rules does not belong anywhere. Since you are concerned with rules, don't forget that the forum have rules too: TERMS AND CONDITIONS FOR USE OF CODEMASTERS WEBSITES You agree not to upload, post, email or otherwise transmit any material which (a) is defamatory, libellous, disruptive, threatening, invasive of a person's privacy, harmful, abusive, harassing, obscene, hateful, or racially, ethnically or otherwise objectionable; or that otherwise violates any law. Codemasters reserves the right to issue warnings, suspend or terminate the registration of users who refuse to comply with these rules. Harassing and flaming other players as cheaters are clearly in violation of the above rules.
  5. Eagleizer

    DiRT Rally 2.0 World Series

    It's 10th September already. What time is the event available?
  6. You wrote this: "I race all cars 100% stock to prove a point and I hold a decently long list of WR's in everything from H2 to 2000cc and GT. But I'm slow compared to the actually fast drivers. The top drivers, who we are expecting to actually make it through qualifiers, are setting times below 3:52 on the current WC stage in Poland with the H2 FWD - they are doing it 100% stock without cuts." Nothing there about you driving without default setup. That is nothing but dishonest. Only reason you say that now, is because you got caught.
  7. You also said: "Therefore the competition remain fair" I had included that in my quote! "Remain", as in it is still fair with fixed setup. But it's not. Because we have different style of driving. How is that difficult to understand? I mentioned more than just scandinavian flick, didn't I? How you st up gear to balance the car in and out of turns is also part of fitting the driving style. This benefits only the drivers who are shy of setups and and have adapted to drive with setus like this. Not saying it is a huge drawback for fast drivers, but It makes it incredibly boring. It is also a valid point that we were not informed about this until today. And steering left and right with full throttle is not what I call rally. It reminds me of rally games 15 years back. And the car is still slow if you can do setup :P It's just more manageable like IRL, and you don't have to torture your engine and yourself with konstant max RPM.
  8. How is it fair when you cannot fit the setup to your driving style? And it is also incredibly boring with a nightmare of RPM throughout the whole stage. It's mostly just steering the car, no skill involved as it is VEEERY slow......
  9. I have seen the document! It's what this thread is about. You said: "We've known about this restriction since the day the World Championship was announced.". My question is where and when whas the link provided? BTW: I loaded up your Ghost at Kopina. How do you explain the you first fly by me at the long stretch in 1st sector, and then fly by me on the stretch in 2nd sector when I am going at full speed, 168 KM/h? And Yes, I did enter the stretch before you, even though you took the shortcut to the right of the tree. Not that I have anything against cutting... Driving with full RPM through the whole stage is nothing but a nightmare for my ears and brain. It's like having my ears filled with wasps. This fixed setups is the stupidest ever, and resembles nothing of real life. That engine would fry long before finish...
  10. Well, than I apologize! But: There were no rules mentioned in the event announcement! They were posted here today AFAIK. But you can easily prove your claim with a link.
  11. You can stop lying right there! I am 2nd, and i do NOT use stock settings. No way any of the other 2 of top 3 is using stock. I can confirm that none of us have been cutting, yet, but how do you know? You are too slow to see if we cut on the last hay ball. My time at the moment is 3:47.062 - All top 10 are below 3:48.924 Limiting setups have nothing to do with finding out who is the good drivers. We have different styles of driving, Scandinavian flick is one, how you use your pedals in coordination with brake balance setup is another. Who is this event for anyway? The fastest, most dedicated drivers, or the casual Sunday driver? Should the fast drivers learn to drive with assists and stupid setups that are unfit for the stage and driving style, or should the novices learn how to drive and adjust gears and other important stuff in the setups?? Is this the World Championship on Sunday drivers? It really makes no sense... And again, applying setup restriction less than 24 hour before the event is just unprofessional.
  12. Totally agree. Different driving styles needs different setups. This is very unprofessional. We have also been practising and working on setups since the announcement, so this restriction comes way too late!
  13. Eagleizer

    Huge rhythmic stutter on high end PC

    The rhythmic stutter is best documented in the Frametime graph. This is using driver 378.92, which is the driver that gives the least stutter. It is sometimes better after a restart, but comes back after a while and eventually the game will hang. Unless I CTRL+ALT+DEL within 10 seconds or so, my whole PC will hang and I have to force close it. I have tried all drivers, 3 different GFX cards (2 EVGA 1080 FTW and GIGABYTE GTX 1080Ti), 2 different MB (ASUS x99 Deluxe and Deluxe II) I have bought a 3rd MB (ASUS ROG RAMPAGE V EDITION 10), but have not tried it yet, because I want to see if the new update 1.5 improves on anything first. Codemasters have been acting worse than I would expect from any dev. in relation to this problem, and is a complete disgrace. So far I have wasted more than $1200 trying to find hardware that is circumventing these BUGs. Codemasters could at least have tried to communicate some statistics and work with us to try to get to the bottom of this problem, but unfortunately, they don't care... Since they asked us to send DxDiag to Support back in february, I have heard NOTHING. Turning OFF all USB does not change anything for me, and using other drivers than 387.92, makes the game totally unplayable. Picture below is with driver 378.92. Frametimes spikes every 10 seconds and there are normally more large spikes in a stage than here. The long line at the end is when the game is windowed in the menu, and inactive. Activating it will trigger the Frametimes seen in the beginning, before I start the stage. The picture is from February 24., but nothing have changed...
  14. They should have kept the whole team until the main BUGs like Stutter, Hang/Force Close and other game breaking BUGs had been fixed. None of these BUGs have even been improved, and more than 12 weeks have passed. "How people still can not comprehend how these things work is beyond me."... Nothing is more important than having a game that is actually playable. FFB and all other stuff is not on that list. It is only on the list for people who are not affected of those game breaking BUGs...
  15. Game still crashes and hang my PC with Access violation that I have reported since 22. February. and TAA OFF still crashes the game if going back to Main Menu, also reported since 22. February:
×