To clarify, I have a point (the origin of my 3d object) and am calculating a directional vector representing the velocity of my object that I can simply add together for the next step in a physics...
Type: Posts; User: Denethor2000
To clarify, I have a point (the origin of my 3d object) and am calculating a directional vector representing the velocity of my object that I can simply add together for the next step in a physics...
Ahh I think I understand the error in my thinking, and I'm glad to see someone has come and pointed it out for me too!
The length of the XY vector [0.5, 0.5] is actually 0.7071, meaning the third...
A 3-element vector representing 3D direction does not include the roll. I believe the 4-element vector that includes the roll is called a quaternion, but I could be mistaken.
The 3 elements in a...
I'm aware of this and this is not a factor in my problem.
Thanks for the links, however the first explains the conversion between quaternions and euler angles and the second explains the...
Sorry for being vague in my wording. What I mean is that a vector with a pitch of 45.0 and yaw of 45.0, of any length, will always have equal elements, just like a vector for a 2d object with an...
I've been looking around for a specific formula to create a Unit Vector representing the direction created by a given Pitch/Yaw.
The formula I see commonly is:
v = [ cos(y)*cos(p), sin(y),...
int main()
{
BYTE Header[500];
fstream file_op("C:\\Test.exe",ios::in);
file_op.getline(Header,500);
for(int i = 0; i < 150; i++)
cout<<"\n"<<hex<<(int)Header[i];
...
Doh, you're right. 1 bit for every digit in the binary. I was thinking 1 bit for each digit in the hex, I don't know why.
Anyway, I'm talking about standard 8bit bytes.
Sorry about that.
Bytes are 2 bits. Words are 4 bits. Dwords are 8 bits. Qwords are 16 bits.
All bytes are 2bit, 0xFF. Stop asking if my bytes are 32bit or 16bit... They're neither, obviously.
Anyway, using...
In C++ language, yes. I use BYTE because it's what I'm actually dealing with: bytes. Less confusing to me, and whoever I share my code with.
Changing it to a char makes 50% of my bytes turn...
It's a struct. Which I included in the same post.
It gets passed to a driver with DeviceIoControl. Which has nothing to do with my problem.
Yeah, I edited that in a minute later, sorry about that.
It's a BYTE array.
BYTE _Buffer[300];
Anyway, I could bypass this problem if I could get my struct to accept a byte array instead of a char array.
struct input
{
UINT_PTR processid;
void *address;
unsigned short int...
I added that comment because last time I spoke of a byte here, the only responses I got were "What's a byte"?
-- If you don't know what a byte is, don't bother reading. --
My program reads/writes the bytes of a program. I specify the bytes to be written [e.g. 0x01 0x02 0x03 0x04] and it writes them to the...
UseDriver _Driver;
bool main(){
BYTE _Buffer[] = { 0xE9, 0xAB, 0x02, 0x00, 0x00 };
BYTE * pBuffer = _Buffer;
//Unrelated junk.
...
Search the text until you find #. Check if Text[CurrentPosition+1] is N and Text[CurrentPosition+2] is #. If not, skip this # and search for the next.
I've done that, which is why I'm asking here.
It's not a compiler error. Everything is correct according to MSDN.
Don't be an ass.
I'm getting error 87 (Invalid parameter) from DeviceIOControl():
#define CTL_CODE( DeviceType, Function, Method, Access ) (((DeviceType) << 16) | ((Access) << 14) | ((Function) << 2) | (Method)...
(BYTE)VarName
I'm pretty frustrated.
I want to use CTL_CODE, which requires the Windev.h header.
Where is Windev.h??
MSDN says it's with CE 4.0 and up.
I downloaded 4.0, updated to 4.2 SP2 and installed...
I don't have access to any but _READ
Can't WriteProcessMemory or ReadProcessMemory without the correct handle.
For example.
This grabs the ReadProcessMemory handle:
m_hProcess = ::OpenProcess(PROCESS_VM_READ, false, _PID)
Yes this is Windows XP.
I've read and written memory to multiple programs. Programs related in no way to mine. A few deny me access.
Could this be a hook they've initialized on the DLL I'm...
Specify what the undesired result is.
If it cuts off at spaces, use cin.getline();