Hi,

I am running a rather high end simulator and have problems to get it running with Ciy Car Driving.

First of all the wheel base - a Simucube 2 Ultimate - is basically not functional within CCD despite I we have set it up also in windows joystick config tool. I CCD the axis seem to be recognized just fine, but the moment the Force Feedbacks starts with the session the wheel just turns uncontrollably to the side. If I deactivate the base during loading and activate it while sitting in the car it kind of works, though. But that's not really a solution for every day use.

We run triple screens and though it is possible to select the full screen resolution of 7680x1440 the pictures in the side monitor are extremely distorted. Also the instructions and messages are shown on the very right side - so well out of regular view. So it's not useable.

Maybe there is a way to improve those aspects in future versions?

best regards,
Bernhard

Hello,

Tripple screen is not supported in the Home edition. For what purpose do you use the simulator?

Regarding the wheel:

We support almost all steering wheels, which are compatible with Microsoft Windows and DirectX. If your wheel has proper driver it should work fine. We recommend wheels with 900 degrees rotation for maximum comfortable gameplay.

If you're using a racing wheel you should set up it properly.

Before starting the game, please perform these steps:

1. Update your wheel driver to the latest version from your controller manufacturer's website.
2. Calibrate your wheel and check if it works correctly in Windows.
3. Please note that you should connect your wheel to the PC and wait until the very end of its auto calibration strictly before(!) launching the simulator.

Then start the game and follow the directions below:

First, check if your wheel has the ready settings preset in the game controls menu. If it has one – just select your wheel from the dropdown list. Everything should work automatically from this point.

If your wheel does not have a ready preset select the “default” preset from the dropdown list. Then you have to assign buttons and axes in the game settings manually. To do that you should double-click with the left mouse button on every action in the list and then push the proper button or pedal on your wheel to assign this button or pedal for this action.

This video explains this process clearly and can help you to setup your racing wheel -

If you're using a gamepad (or any other controller) the procedure is the same.

Hi,

thx for the reply. I planned to use CCD just for fun driving in a city environment as realistic as possible - different to the racing I do normally (with international team in iRacing). For the racing I have proper triple screen setup for 180° view (setup as a large nvidia surround screen..)

I setup the wheel according to the tutorials and it's input is recognized correctly in the config menu. Things go wrong when the game/session starts. It turns all the way to one side uncontrollably. It is also mentioned in the Simucube 2 forum of Granite Devices. So far it's not clear to me if it's a bug in the Simucube Driver, or something in the game Force Feedback output which causes the Simucube 2 Driver to behave like that.. Bottom line, it's not working and the problem is confirmed by other Simucube users.

best regards,
Bernhard

Kivlov wrote:
Developers should add support for triple screens in home edition becouse much people who have steering wheels has a triple screen for realism in home not for enterprise uses.
I know, in russia people don't have money for three monitors but other countries is more rich than russian people...

Hello all,

I'm Mika Takala, the main firmware developer for the Granite Devices Simucube products.

There have been some reports, that the FFB in City Car Driving is indeed less than ideal, and I've just tested this with our internal development boards that output raw data as the device itself sees it.

Here is my report:

The game creates a DirectInput ConstantForce effect and some other effects, that have no relation to funny happenings. Nothing interesting/wrong happens while the game is loading.

When the world finishes loading, the ConstantForce effect's Magnitude parameters is immediately turned to -10000 (maximum negative value) by the game, and this causes the wheel to turn right at full FFB which can be dangerous with these high torque Direct Drive wheels.

If user presses ESC and then "Start again", the same thing does not happen, and something close to believable FFB starts to be produced

I can repeat this all the time with the latest Steam version of City Car Driving.


In other news, the CCD seems to be using so called effect envelopes for Square wave and Triangle wave effects. This makes CCD the first title that uses these canned FFB effects - congratulations on making FFB implementation extra hard on the device-side

In another news, the CCD seems to send new values AND restart effect on each FFB loop iteration for some of the effects. This is certainly not required by the DirectInput specification, and might cause issues in high FFB detail race driving simulators, but certainly does not cause issue here. We know a simple fix to this for C++/DirectInput SDK side - just leave out the restart flag from the SDK call bitmasks if restarting effect is not strictly required.

I hope that we can get into contact with the game developers via this forum.

Mika Takala
Granite Devices

Any comments about the above, @kivlov?

@Kivlov, I am a SimuCUBE 2 user as well, and a long time player of this game. After I got my SimuCUBE 2 base, I was a bit disappointed that the game is not usable with the base at the moment. I would very much love to see you work with @MTakala to add proper support and clear up these incompatibilities with the SimuCUBE 2 system.

@Kivlov
Well, as starter of the thread I obviously support the above posts and hope that you can sort out the existing incompatabilities with each other, so that we can start using your simulator with this wheel base too.

best regards,
Bernhard

MTakala wrote: Hello Mika. Glad to see you on our forum. Thank you for your very detailed feedback. It's very useful. I will forward it to our development team for sure. We will need some time to analyze it.

Just to add, that our wheelbases are not using any custom drivers; we are using the default Microsoft Human Interface Device driver that has all the required functionalities. But as the issue does not seem to happen with wheels that have bespoke drivers, then it also might be a driver bug - for example if you create the effect to the driver but not set any parameters to it, we do not actually know if it leaves the effect variables to strange values that could cause that -10000 torque.

I will be happy to test any debug/test/beta versions.