City Car Driving

City Car Driving

Not enough ratings
[EN] Compilation of Common CCD Errors and Their Solutions
By CCD Team
Error nD3D11Texture / Error 0xc000007b / Error gui_ccd.dll / Simulator Crashes / FPS Drops

Find your error by the chapter title and follow the instructions provided.
If unsure, first check that your computer meets the minimum system requirements, then contact our technical support team at:
online-support@forward-development.ru
   
Award
Favorite
Favorited
Unfavorite
1. Running CCD on Laptops
Important! The simulator is not guaranteed to work on ANY laptops. Due to engine limitations, the simulator may run unstably even on powerful, modern laptops.
We understand that your laptop runs ETS 2 at a stable 300 FPS and other simulators work fine, but different games use different engines—City Car Driving was not designed with laptops in mind.



If you have a laptop with an integrated GPU:

The simulator will not work on such devices.
To run the simulator, you must use a dedicated (discrete) GPU.



If you have a laptop with a dedicated GPU:

There’s a chance the simulator defaults to using the integrated GPU, which may cause launch issues. You can try forcing the simulator to run on the dedicated GPU:
  • Right-click the simulator’s shortcut.
  • In the context menu, select:
    "Run with graphics processor" → "<Your Dedicated GPU>".

Unfortunately, even after this, we cannot guarantee stable performance on laptops due to engine limitations.




2. Starter.exe Error
This is one of the most common errors users encounter.

Before troubleshooting, ensure your PC meets the system requirements. This error often occurs when:
  • Running the simulator on a laptop (regardless of its specs).
  • Using a desktop PC with an integrated GPU.



Solution Steps

Since this issue requires detailed diagnostics, please follow these steps:
  • Take a screenshot of the error in the simulator.
  • Check if any mods are installed (mention this in your email).
  • Generate a DXDiag report (instructions below).
  • Send all the collected data to our support team at:
    online-support@forward-development.ru



How to Create a DXDiag File

  • Press Win + R on your keyboard.
  • In the Run window, type dxdiag and click OK.
  • In the DirectX Diagnostic Tool, click "Save All Information".
  • Save the file in an easily accessible location so you can attach it to your email.


3. nD3D11Texture Error
If the error occurs on a laptop:
Refer to Section 1 of this guide for solutions related to laptops.



[/h3]If the error occurs on a desktop PC:[/h3]

Performance issues are often caused by high graphics settings. Follow these steps to optimize performance:

  1. Adjust In-Game Graphics Settings
    • Set graphics quality to Low or Medium in the simulator’s settings.

  2. Optimize NVIDIA GPU Settings (if applicable)
    • Open the NVIDIA Control Panel.
    • Go to "Manage 3D Settings".
    • Locate the simulator’s profile (or adjust Global Settings).
    • Apply the following recommended settings:
    Antialiasing:
    • FXAA → Off
    • Gamma Correction → Off
    • Settings → None
    • Transparency → Off
    • Mode → Off
    Texture Filtering:
    • Anisotropic Sample Optimization → Off
    • Quality → High Performance
    • Trilinear Optimization → On

  3. Disable Discord Overlay (if used)
    • The Discord overlay can impact performance. Disable it in Discord’s settings:
    • Open Discord Settings → "Overlay" → Toggle "Enable in-game overlay" to Off.


4. Error 0xc000007b
This error indicates issues with system files or restricted access to them

Step 1: Check for Malware
  • Scan your system using Dr.Web CureIt! and Kaspersky Virus Removal Tool.
  • If you have an antivirus/firewall, temporarily disable it or add the simulator to its exceptions list.



Step 2: Verify System File Integrity
  1. Open Command Prompt as Administrator and run:
    sfc /scannow
    Press Enter and wait for the scan to complete.
  2. Then, execute:
    dism /Online /Cleanup-Image /RestoreHealth
    Press Enter and let the process finish.



Step 3: Reinstall Microsoft Visual C++ & DirectX
  1. Uninstall all existing Microsoft Visual C++ Redistributables and DirectX components.
  2. Restart your PC.
  3. Reinstall the required components from:
    • Microsoft Visual C++ (install both x86 & x64 versions):
      \Steam\steamapps\common\Steamworks Shared\_CommonRedist\vcredist\
    • DirectX:
      \Steam\steamapps\common\Steamworks Shared\_CommonRedist\DirectX\
5. gui_ccd.dll Error
This problem most often occurs due to the simulator's installation path.

Make sure the game is installed in a path that contains only Latin characters, without any special symbols. For example, a correct installation path might look like this:
D:\Games\City Car Driving


6. Error "nMesh2: could not open file"
The error you encountered is most likely related to installed mods.

Please note that mods are created by third-party users, and the game developers are not responsible for their functionality. By installing mods, you do so at your own risk.

If the game previously worked correctly but now has issues, the cause is likely incompatible mods or corrupted configuration files.

To resolve the issue, follow these steps:
  1. Unsubscribe from all mods.
    Ensure all mods are disabled or removed via the Steam Workshop.
  2. Uninstall the game through Steam.
    Go to your Steam library, find City Car Driving, right-click and select "Uninstall".
  3. Disable Steam Cloud synchronization.
    • Open the Steam client.
    • Right-click on City Car Driving and select "Properties".
    • Go to the "Updates" tab.
    • Disable the "Enable Steam Cloud synchronization" option.
  4. Manually delete remaining game files.
    After uninstalling the game through Steam, go to the game's installation folder and delete it manually:
    ...\Steam\SteamApps\Common\City Car Driving.
  5. Delete the "Forward Development" folder.
    Go to the "Documents" folder and delete the "Forward Development" folder.
  6. Reinstall the game.
    Install City Car Driving again through Steam.
7. Errors After Installing Mods
Game mods are created by third-party users, and the game developers are not responsible for their functionality. By installing mods, you do so at your own risk.

If the game stopped working after installing mods, follow these steps to fix the issue:

  1. Unsubscribe from all mods via Steam Workshop or remove them manually.
  2. Uninstall the game through Steam:
    • Go to your Steam Library.
    • Right-click on City Car Driving and select "Uninstall".
  3. Disable Steam Cloud synchronization:
    • In Steam Library, right-click on City Car Driving.
    • Select "Properties".
    • Go to the "Updates" tab.
    • Disable the "Enable Steam Cloud synchronization" option.
  4. Manually delete remaining game files:
    • Navigate to the game installation folder:
      ...\Steam\SteamApps\Common\City Car Driving
    • Delete the City Car Driving folder.
  5. Delete the "Forward Development" folder:
    • Go to the "Documents" folder and delete the "Forward Development" folder.
  6. Reinstall the game:
    • Install City Car Driving through Steam.


8. Crashes Immediately After Clicking "Play"
After clicking "Play" in Steam, the simulator starts launching but crashes immediately before reaching the loading screen, without any error messages, and the "Play" button becomes active (green) again.

Most often this problem occurs due to the simulator's installation path. Make sure the game is installed in a path that doesn't contain Russian characters. For example, a correct installation path might look like this:
D:\Games\City Car Driving

If this doesn't help - contact technical support:
online-support@forward-development.ru


9. No Instructor Voice in Simulator
To fix this issue, we recommend performing the following steps:

  • Set the desired language in the simulator settings. Close the simulator.
  • Unsubscribe from all mods.
  • Disable Steam Cloud synchronization for City Car Driving. To do this, open the Steam client, right-click on City Car Driving and select "Properties" from the context menu. Then go to the "Updates" tab and disable the "Enable Steam Cloud synchronization for City Car Driving" option.
  • Delete the "Forward Development" folder from the "My Documents" folder.
  • Launch the simulator.


10. Control Device Calibration
Before calibrating your steering wheel, you must delete or rename all configuration files located in the Forward Development folder.
This folder is located in the "Documents" folder on drive C.

After completing this step, restart the simulator. If the issue persists, perform manual calibration of your steering wheel and controls by following these instructions:

  1. Check Drivers:
    Ensure you have the latest driver version installed for your steering wheel.
  2. Connect Steering Wheel:
    Connect your steering wheel to the computer before launching the simulator.
  3. Configure Controls:
    After launching the simulator, assign in-game actions to your steering wheel buttons and axes in the control settings section.
    • Note: Use double-click to assign buttons, not single-click.
    • Detailed control configuration instructions are available in the user manual installed with the application, located in the program folder via the START menu.
11. Logitech Profiler Doesn't Detect Wheel
Logitech Profiler doesn't detect the wheel due to Windows 11 security settings.

  1. Disabling Windows 11 security features:
    • Press the "Start" button.
    • Go to "Settings" → "Privacy & Security" → "Windows Security" → "Device Security".
    • In the "Core Isolation" section select "Core Isolation Details".
    • Disable the following security features:
      "Memory Integrity"
      "Vulnerable Driver Blocklist"
  2. Removing Logitech devices:
    • Open Device Manager.
    • Find and remove all Logitech devices.
  3. Removing Logitech Gaming Software:
    • Press the "Start" button.
    • Go to "Settings" → "Apps" → "Installed Apps".
    • Find and completely remove the "Logitech Gaming Software" application.
  4. Rebooting and installing drivers:
    • Restart your computer.
    • Connect the wheel to power and USB port.
    • Reinstall Logitech drivers.