Add other trace_t members into TraceResult
This commit is contained in:
parent
2d32412819
commit
60c1273145
6 changed files with 320 additions and 244 deletions
10
README.md
10
README.md
|
|
@ -119,12 +119,6 @@ bool LoadRayTrace()
|
|||
|
||||
### C# (CounterStrikeSharp plugin)
|
||||
|
||||
There are **two ways** to use the managed side:
|
||||
|
||||
1. `public/Example.cs` (reference implementation, for learning / custom
|
||||
binding)
|
||||
2. **Official release packages (recommended)**
|
||||
|
||||
The recommended way is to use the prebuilt release components:
|
||||
|
||||
- Install **RayTraceImpl** as a CS# plugin:
|
||||
|
|
@ -138,9 +132,6 @@ The recommended way is to use the prebuilt release components:
|
|||
Then reference `RayTraceApi.dll` in your own plugin project and call the
|
||||
API normally.
|
||||
|
||||
`public/Example.cs` demonstrates manual binding and struct layout, but
|
||||
in production you should rely on the release bridge + shared API.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
## Calling methods from C++ (Metamod)
|
||||
|
|
@ -242,7 +233,6 @@ Due to C++ ABI differences:
|
|||
| Linux (Itanium ABI) | 2 | 3 | 4 |
|
||||
| Windows (MSVC ABI) | 1 | 2 | 3 |
|
||||
|
||||
`public/Example.cs` shows how offsets are applied manually.\
|
||||
Release builds handle this automatically inside RayTraceImpl.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue