Jump to content

MBastieK

Members
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

23 Unleaded

Recent Profile Visitors

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

  1. I think this whole SpaghettiCodeMasters product is more a bad emulation, than a simulation, which leads to a lot of unnecessary coherences and stupid bugs. The driving physic seems an emulation too. After testing and playing the RBR tarmac physics, I don't want to play Dirt Rally 2.0 anymore. In 0.59 updates we have finally Dirt Rally 2.0, maybe then I give it a try again. I mean SpaghettiCodeMasters has more than 30 years experience and almost 50 Racing-Games and they can't even implement an intelligent and optionalizable viewing-line, where you can see the vibrations of the car, but still have a kind of stable viewing-line to the horizon. Or they can't or don't create tarmac tracks, which are lively with a lot of micro- and macro-bumps and unformed track-shape. No, the tarmac-tracks are just smooth, which is also a hint for me, that this product is just an emulation, without e.g. modern tire-deformation-physics. A good software-architecture could lead to a good optionalizable and extendable game. I think they use new developers for this niche product, and if they are good developers, they can promote to the F1 201x programming. Greetings
  2. A bug can be a hint for solving another bug. Coherence. Greetings.
  3. MBastieK

    Pacenote editor

    Yes more optionality in this game would be great. This needs a good software-architectur. If I experienced right, all cars have the same pacenotes. I think adapted to the 2000's. With a Group B car all pacenotes have to be interpreted with caution. Greetings.
  4. MBastieK

    DiRT Rally 2.0 - V1.2 - found a bug? Post it here!

    Seems normal, when vSync (or modern alternatives) is off. Greetz.
  5. MBastieK

    DiRT Rally 2.0 - V1.2 - found a bug? Post it here!

    The sound bug only happens to me in New Zealand. Version 1.1 and 1.2. Complete sound loss. Sometimes cracking after loss. Sound loss after short playtime. Greetz
  6. MBastieK

    DiRT Rally 2.0 - V1.2 - found a bug? Post it here!

    Maybe because you didn't start as last driver? It seems you started as 2nd driver. Greetz.
  7. MBastieK

    DiRT Rally 2.0 - V1.2 - found a bug? Post it here!

    I have framedrops (to half fps) too, since updated to 1.2. The game also is using only 4 of my 8 cores. Seen in task-manager and in config-file: threadStrategy: workerMap4Core.xml is only used. Dirt Rally 1 used workerMap8Core.xml with the additional more-core options set. Greetz
  8. MBastieK

    DiRT Rally 2.0 - V1.2 - found a bug? Post it here!

    Related to all new controller binding problems. I had to edit the (E:\[Games]\DirtRally2.0\)...steamapps\common\DiRT Rally 2.0\input\devices\device_defines.xml file to get my Controller working again. Maybe adding or editing the files in (E:\[Games]\DirtRally2.0\)...steamapps\common\DiRT Rally 2.0\input\actionmaps can help too. I didn't do it, because I used a exisitng file in there for my virtual Joystick(vJoy) problem. In "dxdiag" i checked the VendorID and ProductID of my vJoy-Controller and added <device id="{BEAD1234-0000-0000-0000-504944564944}" name="ftec_clubsport" priority="101" type="wheel" /> to (E:\[Games]\DirtRally2.0\)...steamapps\common\DiRT Rally 2.0\input\devices\device_defines.xml file. Beware of ProductID and VendorID order: my: ProductID: BEAD , VendorID: 1234 I misused "ftect_clubsport" actionmap/name for first try and it worked. I still think Codemasters did a "bug" with these files. Actually this bug also helped me understand and solve an older individual problem, which I had with vJoy and Input-Output-Linearity. Thanks. Greetz
  9. I had to edit the
    (E:\[Games]\DirtRally2.0\)...steamapps\common\DiRT Rally 2.0\input\devices\device_defines.xml
    file to get my Controller working again.


    Maybe adding or editing the files in 
    (E:\[Games]\DirtRally2.0\)...steamapps\common\DiRT Rally 2.0\input\actionmaps
    can help to. I didn't do it, because I used a exisitng file in there for my virttual Joystick problem.

    Greetz

    1. T3ddy

      T3ddy

      yes thanks, i add this line in mine for Leo Bodnar card:

      <device id="{10A01DD2-0000-0000-0000-504944564944}" name="Logitech® G25 Shifter" priority="100" type="handbrake" />

      Thanks for your message !

  10. MBastieK

    DiRT Rally 2.0 - V1.2 - found a bug? Post it here!

    After update to 1.2, my vJoy-Controller isn't registered anymore. That means "vJoy Device" is still in "Connected Devices", but inputs aren't registered anymore to bind inputs to behaviour. (In "Advanced Settings" in my "vJoy Device" "Steering Sensitivity" and others are only optionalizable with analog adjuster, but not with left/right-adjuster (left/right arrows) - bug!?!) I can't play anymore. And "Darkness issue resolved when using interior cameras" doesn't seem to work either. But who cares, I can't drive, because of no vJoy-inputs. And because of modern times, I can't use Version 1.1. vJoy = virtual Joystick (driver) to bind mouse movement, mouse-buttons or other input devices to a virtual (analog) joystick. Dirt Rally 2.0 Version 1.1 was running fine with vJoy. Others in this thread have controller-binding problems too. I think it is a more general issue.
  11. MBastieK

    DiRT Rally 2.0 - V1.1 - found a bug? Post it here!

    After update to 1.2, my vJoy-Controller isn't registered anymore. That means "vJoy Device" is still in "Connected Devices", but inputs aren't registered anymore to bind inputs to behaviour. (In "Advanced Settings" in my "vJoy Device" "Steering Sensitivity" and others are only optionalizable with analog adjuster, but not with left/right-adjuster (left/right arrows) - bug!?!) I can't play anymore. And "Darkness issue resolved when using interior cameras" doesn't seem to work either. But who cares, I can't drive, because of no vJoy-inputs. And because of modern times, I can't use Version 1.1.
  12. What's the philosophy behind the static camera? In the current case the driver is like a robot with static eyes. The human eye and the human brain(-"algorhythms" are) is flexibel, so that a static shaking is compensated with a smoother and concentrated view to a point in the front. The car can still shake and vibrate around this not so strong shaking viewing-line. Thats kind of unplayable. Drivers are not body-, neck- and eye-static robots. Maybe it's a bug. Changing "Camera shake" in preferences has no effect. The rest is a good game for me. Greetz.
  13. MBastieK

    DiRT Rally 2.0 - V1.1 - found a bug? Post it here!

    In preferences (PC version): Changing "Camera Shake" to completely "No Shake" doesn't seem to have an effect. Changing "Co Driver Calls" to earliest doesn't seem to have an effect. With "Camera Shake" my 100 fps(frames per seconds) seem/feel like 30 fps. Edit: Changing "Co Driver Calls" to completely "Later" makes the co-driver to call calls earliest. This Problem/Bug kind of solved. Hehe. Edit2: Sorry, misinterpreted co-driver calls semantic; there is no bug. Greetz
×