Let’s get you
back on the road.

First load your actual driving profile and return to gameplay. TAB will not behave as the tablet shortcut while another menu owns input. Check the current plugin is installed in the selected game, activation is valid, and both required game settings are enabled.

1. Close ATS and ETS2 before installing or repairing files.
2. In the installer, select the correct game and use Install plugin. Avoid duplicate old Huxxi plugins.
3. Under Settings → Game fixes, enable console/developer mode and run Fix tablet keyboard.
4. Restart the game and load the intended profile. If TAB still fails, use the controls.sii check below.

The correct device name is sys.keyboard, not keyboard.sys. Some affected profiles use di8.keyboard, which can prevent the tablet keys from working. The installer’s Settings → Game fixes → Fix tablet keyboard changes that device entry and keeps a one-time backup.

1. Close the game so it cannot overwrite the change.
2. Prefer the installer repair. For a manual repair, back up the active profile’s controls.sii first.
3. In a readable text controls.sii, replace the exact device text di8.keyboard with sys.keyboard. Keep the surrounding syntax and other bindings unchanged.
4. Restart and load that profile. Do not try to edit an unreadable/binary file as text.

Look in the selected game’s actual home folder, under profiles or steam_profiles and then the profile’s folder. It is not the Steam installation folder. OneDrive, a moved Documents folder or a custom -homedir may change the location. Check the installer’s Game home directory and load the intended profile before diagnosing it.

The repair targets the keyboard device name in readable profile controls files; it does not replace your complete control layout. The one-time backup is named controls.sii.huxxi-backup. Keep it before making further manual changes, and close the game during the repair.

Yes. Set the existing config.cfg entries to uset g_console "1" and uset g_developer "1" in each game you use. The installer’s Game fixes section can enable them with the game closed. If editing manually, keep the .cfg extension, avoid duplicate entries and restart.

Saved bindings take priority over defaults. Check Settings → Key bindings and the relevant movement, cabin or trailer/job group. Use the configured walk toggle for entry/exit; there is no second F-to-enter shortcut. Match any game Attach, lights, wipers and engine bindings to the active game profile.

Click back into the game/tablet, close conflicting menus and check that you are using the current plugin. Try the keyboard repair if the problem is profile-specific. Mouse, controller and keyboard paths are supported, but a key held across focus changes may need to be released before trying again.

Confirm the device is connected and bind it in Huxxi Settings. Device identity and saved bindings matter if hardware was replaced or reconnected. Short presses are retained between game frames; avoid mapping the same button to conflicting actions. A configured game action still needs the corresponding in-game keyboard binding.

Generate a compatibility pack before expecting Huxxi locations. In that profile’s Mod Manager, put exactly one matching Huxxi Roleplay Map Compatibility pack at the TOP, above its source maps. Disable older Huxxi icon packs and add-ons; keep the original maps and dependencies below it in their authors’ required order.

1. Load the intended profile once, then close the game.
2. Select the correct game/home in the installer and choose Find my maps.
3. Review the sources, then Generate & install for that setup.
4. Enable its matching pack at the top of that same profile. Do not enable several generated packs together.

The map pack supplies locations; the activated gameplay plugin handles interactions. Check that both are installed and the matching generated data is available. Walk to the actual interaction area and use your saved shop key when prompted. A bus-stop icon is a discovery/pickup point, not a shop. Reviewed coordinates do not guarantee a measured doorway for every custom building.

Each game has its own installation, home and generated data. Generate for the correct ETS2 profile rather than copying ATS data. Confirm the matching pack is enabled, and do not diagnose an empty location catalogue before generating the map. Wrong-game, missing or stale data is rejected instead of borrowing another profile’s locations.

The installer installs the generated SCS in the game home’s mod folder and its matching data at bin\win_x64\plugins\hxdata\<setup>\data.hxdb inside that game’s installation. The base setup uses base. Keep the generated names unchanged. Old root-level plugins\data.hxdb is no longer loaded.

Yes. Leave the setup identifier blank for the base game and official DLCs; choose a different short identifier for each modded combination. Keep multiple setups installed, but enable only the matching generated pack in each profile. ETS2 and ATS store their data separately.

Open the intended profile, enter gameplay, then close the game before scanning. The installer reads that session’s game.log.txt. Check the selected game home contains that log, profiles and mod. A stale log or another game’s home can describe a different setup; game.crash.txt is not the map-source list.

Regenerate after a game version, map source, active mod list or load-order change. Moving from an older generated data format also needs a one-time regeneration. A plugin-only, audio or artwork update normally does not require rebuilding an otherwise matching pack.

The scanner recognises reviewed service models. An unfamiliar custom building can remain unclassified even when its archive is readable. Report the map name, location and a screenshot through support. Generating markers does not add universal building recognition or navigation coverage.

Use the current installer and read the Activity error rather than the percentage alone. A reported missing-source-sector failure near unavailable DLC areas has a specific filtering fix. Other failures can involve unsupported sectors, unreadable archives, missing dependencies, permissions or space.

1. Use Activity → Open diagnostic log or Open logs folder.
2. Check the highlighted source/member and confirm the map combination works in the game.
3. If removing a bad source, disable it and its required dependants in Mod Manager, load the working profile, close the game, and scan again.
4. Send the scan log and exact error to support if it still fails.

No. It only excludes Huxxi icons from that source. Active geometry and model definitions still resolve in the profile’s load order. Disable an unwanted map in the game and capture the revised profile before generating again.

No. The reader supports known game-readable ZIP and HashFS variations, but damage, unsupported compression and unsupported sector formats are different problems. A genuine encrypted payload still needs an authorised readable version. Do not change sector headers or generate from an older hidden source to bypass an error.

TaxiConnect conversation alone does not fit a visible rider into every car. On a supported ATS Road Trip car, you also need the optional Real Cab Passengers companion and the TaxiConnect Seats accessory.

1. Enable Real Cab Passengers above the supported car/accessory packages in the active profile.
2. Use a supported Road Trip Bronco, F150, Mustang or Crown Victoria.
3. Visit the interior upgrade shop, add TaxiConnect Seats to the car and CONFIRM the purchase.
4. Start an eligible TaxiConnect ride and wait until boarding finishes. A passenger is not permanently shown between rides.

No. The prepared ETS2 appearance library does not provide universal car fittings. A compatible vehicle/seat fitting is still required; enabling a model library alone cannot place a rider in a car. Third-person player characters and visible taxi occupants are separate features.

Use the matching current passenger companion, car package and seat fitting. The plugin retries a missing appearance before selecting a recognised compatible appearance of the same gender. This cannot mount a missing companion or make an unsupported car compatible. Include the current game log when reporting it.

Park inside the indicated 100-metre arrival area, stop, turn the engine off, apply the parking brake and stay inside. Wait for the pickup/drop-off countdown. Moving or breaking the parking conditions can reset it. A direction pin is not permission to drive through a barrier.

Load and activate the game, finish the current delivery job, and check phone battery and mobile credit. Offers also need reachable sites and supported routing data for the setup. A shop marker catalogue does not automatically supply every custom map’s road network.

An occasional eligible longer ride can request a named friend pickup. It uses another supported seat and appearance; the friend adds half the normal rate after joining. It is a random situation, not a permanent second passenger. The vehicle and companion still need the appropriate fittings.

Open TaxiConnect → Job history for the rating factors and payment breakdown. Collisions, confirmed fines, missed requested stops and poor hygiene can affect the score. Repeated driving habits have grace allowances. Tips vary with rating and personality and need collision-free eligibility. Cleanliness or laundry below 10% can trigger a 100 USD/EUR drop-off deduction.

Choose Quiet, Normal or Chatty under Settings → AI Settings → TaxiConnect. New pacing spreads optional events through the trip and reduces repeated starters. Generated wording can still recur. If reporting a duplicate, say whether it was pickup, boarding, driving or drop-off, and whether two copies of the plugin were installed.

A rare completed ride can produce a return opportunity after a delay while you remain online and take no other job. Follow the return pin and park as instructed for a separate reward and thank-you. Accepting another ride/job or the return timeout ends the opportunity.

Their sidebar apps remain separate. Open Settings → AI Settings, then choose TaxiConnect or TruckMate. Configure passenger chattiness/language in TaxiConnect, and your key, voice, microphone and companion preferences in TruckMate.

Load models using your own key. Only supported voice-capable Live models available to that key are selectable. Availability changes; reload and choose another supported Live entry if one disappears. Text-only models are not a substitute for live voice.

Check internet, a valid key, supported Live access, phone battery above zero and mobile credit of at least 1.00. Google quota and billing are separate from game money and phone credit. Keys in the same Google Cloud project share quota; extra keys do not automatically add capacity.

Select the intended input under AI Settings → TruckMate and use Test microphone. Check Windows microphone privacy permission for desktop apps, the device mute and whether another app opened it exclusively. Hold the configured talk key in gameplay and release to send.

Set Huxxi’s lights, wipers and engine keys to match the active game profile. Sit in the driver’s seat, make an explicit ON request and close the tablet so the game can receive the action. Starting the engine first requires safe parking and a valid engine binding. Already-on controls are not toggled off.

No. It adds Huxxi guidance to a suitable stop ahead while keeping the main destination. It does not write a native game GPS waypoint. Places and road coverage must exist in the supported datasets; a pin does not establish barrier-free access.

Confirmed collisions and extremely close traffic take priority over casual speech, but a Live response still needs model access and network processing. Queues, cooldowns, phone state or unavailable service can prevent a line. The assistant cannot confirm a distant unseen accident.

Park safely, move to the bunk and settle into the lying position. You need a usable pillow, blanket and fan; a missing or worn-out item blocks a cabin nap. The old free-standing cabin F-to-sleep shortcut is not the rest flow.

Use Shift+R for driver-seat recovery and check the current plugin. It cancels a nap and restores the saved driver camera. Cab-specific geometry, camera/head-tracking mods and clearance can affect the view. Report the truck/cabin and camera setup if the position remains wrong.

Check the character selection and body/view bindings in Settings. Install current matching generated character assets above the maps. First-person head hiding and restricted body visibility while looking toward the windows/back are intentional to limit clipping. A missing model asset needs the matching pack, not just another camera toggle.

Low vehicle surfaces use a physical jump; reachable higher edges can use a climb or vault. Detection requires usable collision, clearance and a supported landing. Decorative meshes, excessive height, blocked landings and world boundaries can remain unavailable.

Follow the active checklist step and its marker. Check Trailer & job papers settings, move within the prompt’s range, and use the configured interaction key once. A native failure should leave a reason and allow deliberate retry; audio alone is not confirmation. Confirm the game’s Attach binding is correct and avoid repeatedly toggling it.

Update to the current plugin. The repaired check accepts the required forward-throttle hold as well as short forward travel: engine on, forward gear, parking brake off and continuous throttle. Reverse, neutral, walking or the brake being on cannot pass it. Follow the displayed tug-test prompt.

Enable job markers in Trailer & job papers settings and check the active stage. Points are derived from the trailer hook/wheel placement, with guidance when off screen. A modded trailer can need further validation; share its name, stage and screenshots rather than forcing game actions.

Use the current plugin and a compatible game/trailer setup. These steps depend on checked native actions and cable graphics; an unsupported hook or disabled cable rendering cannot be fixed by replaying audio. Read the step’s reason, retry deliberately when safe and include the game log if it repeats.

The revised flow uses bill-of-lading/CMR papers and delivery confirmation instead of parcel loading into the car. Follow the foreman/paperwork marker. If an older parcel flow remains, confirm you are running the current installation rather than a duplicate older plugin.

Use the current plugin and wait for the reader to appear before the tap/PIN stage. Check focus and close conflicting menus; keyboard, numpad and the displayed keypad use the same payment controller. A cancelled or failed purchase must not be treated as approved. Report the exact stage and game log if it stalls.

Close and reopen the tablet after changing its Graphics profile. Compare the private hardware and software options on your setup; neither is universally faster. Current changes reduce redraws, transfers and routine saves while retaining full-resolution payment art. Share the game log, GPU and graphics-mod list if degradation continues.

Close both games and use Install plugin for the intended installation. Normal installation preserves saves, activation and preferences. Keep your own profile backup. Generate again only for a changed game/map/load order or an older incompatible data format; enable the matching pack afterwards.

Compatibility checks reduce unsafe assumptions, but no mod can promise every future native game layout. Models, generated map sectors and memory-dependent actions have different update requirements. Use the current release notes; unsupported native actions can stop until a compatible patch is available.

Include game and plugin release, the active map/profile setup, vehicle/cabin or trailer, exact action/step, error and screenshots. Use the latest game.log.txt and game.crash.txt for a crash, plus the installer diagnostic log for map failures. Check local paths before sharing. Never send licence/API keys, payment PINs or unrelated personal files.