Forums WoW Modding Support Archives TrinityCore Discord Archives [DiscordArchive] So how about details on that specific issue?

[DiscordArchive] So how about details on that specific issue?

[DiscordArchive] So how about details on that specific issue?

rektbyfaith
Administrator
0
08-11-2024, 11:30 AM
#1
Archived author: gemini • Posted: 2024-08-11T11:30:19.951000+00:00
Original source

So how about details on that specific issue?
rektbyfaith
08-11-2024, 11:30 AM #1

Archived author: gemini • Posted: 2024-08-11T11:30:19.951000+00:00
Original source

So how about details on that specific issue?

rektbyfaith
Administrator
0
08-11-2024, 11:36 AM
#2
Archived author: Fabian • Posted: 2024-08-11T11:36:30.447000+00:00
Original source

Fix your os install/3rd Party programs
rektbyfaith
08-11-2024, 11:36 AM #2

Archived author: Fabian • Posted: 2024-08-11T11:36:30.447000+00:00
Original source

Fix your os install/3rd Party programs

rektbyfaith
Administrator
0
08-11-2024, 01:29 PM
#3
Archived author: gemini • Posted: 2024-08-11T13:29:04.180000+00:00
Original source

I was able to clone the repo- and also successfully build it with the latest open source launcher...
I also changed the low-level Read() to get & output LastWin32Error:

public byte[] Read(nint address, int size)
{
try
{
var buffer = new byte[size];

if (ReadProcessMemory(_processHandle, address, buffer, size, out var dummy))
return buffer;
else // else - throw added for troubleshooting ReadProcessMemory() issues
throw new Exception($"ReadProcessMemory() = FALSE : GetLastError() = {Marshal.GetLastWin32Error().ToString()}");

}
catch (Exception ex)
{
Console.WriteLine(ex.Message);
}

return null;
}

Issue with using this is I don't believe this version supports your client version. So in order to go this route you'd have to use an earlier client with this launcher version and see if it ALSO errors out on your machine- if so it's a fair bet that they are both experiencing the same issue (but not a guarantee).

This IS preferable as it would line up much closer to what the current launcher is doing when attempting to Read/Write to the client's memory.
rektbyfaith
08-11-2024, 01:29 PM #3

Archived author: gemini • Posted: 2024-08-11T13:29:04.180000+00:00
Original source

I was able to clone the repo- and also successfully build it with the latest open source launcher...
I also changed the low-level Read() to get & output LastWin32Error:

public byte[] Read(nint address, int size)
{
try
{
var buffer = new byte[size];

if (ReadProcessMemory(_processHandle, address, buffer, size, out var dummy))
return buffer;
else // else - throw added for troubleshooting ReadProcessMemory() issues
throw new Exception($"ReadProcessMemory() = FALSE : GetLastError() = {Marshal.GetLastWin32Error().ToString()}");

}
catch (Exception ex)
{
Console.WriteLine(ex.Message);
}

return null;
}

Issue with using this is I don't believe this version supports your client version. So in order to go this route you'd have to use an earlier client with this launcher version and see if it ALSO errors out on your machine- if so it's a fair bet that they are both experiencing the same issue (but not a guarantee).

This IS preferable as it would line up much closer to what the current launcher is doing when attempting to Read/Write to the client's memory.

Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)