> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/cyberpunk-2077-modding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/vehicles/boe6s-guide-new-car-from-a-to-z/boe6s-vehicles-extra-details.md).
# Boe6's vehicles: Extra Details
Minor details that didn't deserve a whole page
### Wheel Audio Components
Each wheel on your vehicle has it’s own audio component for sound. Position data path:
```
.ent file > RDTDataViewModel > components > WheelAudioEmitterFL/FR/BL/BR
```
### Vehicle Exhaust Alignment
Vehicles use FX emitters on the exhaust for visual effects. These positioning values need to be configured as well.
```
.ent file > RDTDataViewModel > components > FX_slots > slots > fx_exhaust_x
```
### Engine Damage FX Smoke
FX emitters need to be positioned for smoke effects when vehicle damage occurs
```
.ent file > RDTDataViewModel > components > FX_slots > slots > fx_engine
```
### Wheel Fire FX position
Each Wheel has a fire FX position to be configured
```
.ent file > RDTDataViewModel > components > FX_slots > slots > fire_fr/fl
```
### Vehicle Handling
Needs more research. Some control is set in tweaks.
Check Tweaks: `gamedataBaseDrivingParameters_Record` under `driving`
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/vehicles/boe6s-guide-new-car-from-a-to-z/boe6s-vehicles-extra-details.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
