Jump to content

MBastieK

Members
  • Content Count

    25
  • Joined

  • Last visited

Everything posted by MBastieK

  1. 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.
  2. 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
  3. A bug can be a hint for solving another bug. Coherence. Greetings.
  4. 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.
  5. I think you must also change the name. And I put my device at the beginning of the list. With name="ftec_clubsport". And try a higher priority. And no default-tag. I think, id or name "xinput_pad" has a special coded treatment. There is a high chance for failures, when changing or playing with this tag. Like I kind said, put an individual tag at the beginning of the list. (But I once deleted the mouse tag, and the game still worked without mouse.) And you could still map your controller to a virtual joystick (vJoy + UCR). Try to think about fine solutions. I still see a lot of possibilities and permutations. Don't give up. Greetz.
  6. Maybe don't do it via id="xinput_pad". Use/add your individual id found in dxdiag. Should then be look like id="{BEAD1234-0000-0000-0000-504944564944}". Beware of ProductID and VendorID order: my: ProductID: BEAD , VendorID: 1234. Greetz
  7. With Linearity 0 in preferences, you have full raw input. Try Linearity 1 or 2, now you have set your controller to "wheel". Linearity 10 is full assisting again. (Kind of twisted semantic.) Negative Linearity is not recommend. To twitchy. Might be, that Linearity -10 is now your standard. With the software UCR and vJoy you could map your Controller to a virtual joystick, and write a script, which fits your personal requirements. Speed reduction is of course not doable there. Greetz
  8. As I said, you can configure your controller to raw input by configuring it to "wheel" in device_defines.xml. In "dxdiag" you can check the VendorID and ProductID of your Controller and add <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 think you can choose whatever you want for "ftec_clubsport". Or maybe you can configure your controller directly to "wheel" ingame. "Wheel" is raw input for every input-device. And if you would quote or thumb up the others or me, the others or I would see your reactions here by getting a message. So that the others or I don't have to follow you or this thread to help you. Greetz.
  9. Maybe you can edit the (E:\[Games]\DirtRally2.0\)...steamapps\common\DiRT Rally 2.0\input\devices\device_defines.xml file to get your Controller working. In "dxdiag" you can check the VendorID and ProductID of your Controller and add <device id="{BEAD1234-0000-0000-0000-504944564944}" name="ftec_clubsport" priority="101" type="handbrake" /> to (E:\[Games]\DirtRally2.0\)...steamapps\common\DiRT Rally 2.0\input\devices\device_defines.xml file. Type can also be "pad", "wheel",... Beware of ProductID and VendorID order: my: ProductID: BEAD , VendorID: 1234 Greetz
  10. Ok. Thanks. I just don't want the game too easy. But if this is IRL Codemasters could make things like that in a good software-architectur optionaliziable. Greetz.
  11. And they also use/add it for co-driver pace-note calls? Greetz.
  12. Ok, thanks for info. What tyres to take and written and called on pace-notes, I think!?! Thanks. Greetz.
  13. Patches of ice are temporary nature-objects. I don't think, they should be on the noticepad (notice-block) of the co-driver or called out from co-driver. Greetz.
  14. If you play on PC, you can set your controller to wheel (or edit the device_defines.xml). Then you have complete linearity, but you loose the reducements, which makes driving at high speed safer. Greetz.
  15. MBastieK

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

    Seems normal, when vSync (or modern alternatives) is off. Greetz.
  16. 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
  17. How about an extra semi-automatic option in GameSettings->Assists->Transmission options, which is on automatic, when driving forward. But to switch in reverse-gear, someone has to use his gear-down-key (button or what liked). And gear-up-key for back to 1st gear. So I can drive backwards/reverse with the help/use of my accelerate-pedal (or accelerate-button) and so I can use brake-pedal (or brake-button) to brake, when I drive backwards. So it would things make more naturally and allows to brake when driving/rolling backwards. Now I use (full) automatic. Greetz.
  18. 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.
  19. 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
  20. 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
  21. 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 !

  22. 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.
  23. 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.
  24. In real life every driver can color the the middle of his steering wheel with a colored tape. I need this, because I drive/steer with mouse and I need the rendered cockpit steering wheel to know better when steering is middled. Thank you. Greetz
  25. 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
×