Jump to content

MBastieK

Members
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

17 New Car Smell

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. 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.
  5. 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
  6. 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
  7. 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.
  8. 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
  9. MBastieK

    Rally Monte Carlo general feelings..

    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.
  10. MBastieK

    Rally Monte Carlo general feelings..

    And they also use/add it for co-driver pace-note calls? Greetz.
  11. MBastieK

    Rally Monte Carlo general feelings..

    Ok, thanks for info. What tyres to take and written and called on pace-notes, I think!?! Thanks. Greetz.
  12. MBastieK

    Rally Monte Carlo general feelings..

    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.
  13. 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.
  14. Seems normal, when vSync (or modern alternatives) is off. Greetz.
  15. 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
×