[Swoorup]

Yeah, to make it work for any vehicle,
I believe this one would work.

Cam.x+=10.0f
Cam.y+=10.0f
Cam.z+=4.0f
Memory location are documented on GTAModding.com site in Memory Address
Any idea what Strechnutter has done for his Cam hack tool?

[Swoorup]

CODE

struct CPed { 0x338 CPathNode* CurrentWanderingNode; 0x33C CPathNode** NextWanderingNode; };

There might not be easy way to increase the paths. The path's coordinates from ipl file is truncated and is multiplied by 8 (after multiplying it by 1/16) and stored in a signed 2 bytes space in PathNode struct.
Now the signed values have limits ranging from -32767 to 32767. So the limits for path coords would be -4095 to +4095 after division by 8.
The 16 bit limit is same for GTA SA and the values are stored after multiplying by 8

QUOTE

GTA Vice City From (-2300,-1900,-INF.) to (1540,1900,INF.) approximately, standard units. Total area: 14.6 square kilometers. GTA San Andreas From (-3000,-3000,-INF.) to (3000,3000,INF.) standard units. Total area: 36.0 square kilometers

The 16x multiplier hack may be able to increase the original limits but it would increase not above that number.
The solution to this may be redirecting every function that accesses this struct. But that would of course take a very long time.

CODE

struct CPathNode //size 0x14 { _uint16 unk1; Always 0xFFFF _uint16 unk2; Current Index? _int16 x;  Divided by 8 _int16 y; _int16 z; _int8 unk3; _int8 unk4; _int16 nextPointIndex; _int8 unk5; _int8 unk6 _int8 flags; _int8 unk7 _int8 unk8 _int8 unk9; }

As for the nodes not connecting properly after 16x multiplier hack, It might have to do something with the closest Node search radius. This function CPathFind::FindNodeClosestToCoors returns -1 if the node is not found. If it finds it would return a pointer to a pathnode struct.

This might be occuring with the vehicle paths only since the peds path are close to each other in every nodes (Or most of the nodes I should say). Vehicles node tends to break up in a straight highway since the nodes are placed very far to each other.
Also there might be an angle problem while taking a turn.
I have not seen this issue with peds path though.

I have fairly decompiled that function.

CODE

signed int __userpurge CPathFind__FindNodeClosestToCoors<eax>(GlobalMap *global<ecx>, signed int curObjecttypetIndex<ebx>, signed int LastObjecttypeIndex<edi>, float x, float y, float z, char type, float searchRadius, char skipForbidden, char flag2, char flag3, char flag4) {  signed int v12; // esi@1  double v2; // st5@1  double VfY; // st7@1  signed int _curObjecttypetIndex; // ebp@4  CPathNode *curRouteNode; // edx@5  int curRouteNodeOffset; // ebx@5  double curRouteNodeY; // st3@13  float curRouteNodeX; // ST0C_4@16  double v3; // st2@14  double v21; // st2@16  double xOffset; // st3@16  double yOffset; // st4@16  double curRouteNodeZOffset; // st6@18  double zOffset; // st2@19  double v26; // st6@21  signed int result; // eax@25  v12 = 0;  VfY = y;  v2 = f10000;  switch ( type )  {    case 0:                                     // For vehicles      curObjecttypetIndex = 0;      LastObjecttypeIndex = global->lastVehicleRoutePointIndex;      break;    case 1:                                     // For Peds      LastObjecttypeIndex = global->lastPedRoutePointIndex;      curObjecttypetIndex = global->lastVehicleRoutePointIndex;      break;    default:      break;  }  _curObjecttypetIndex = curObjecttypetIndex;  if ( curObjecttypetIndex < LastObjecttypeIndex )  {    curRouteNodeOffset = 20 * curObjecttypetIndex;// Since size of CPathNode is 0x14 = 20    curRouteNode = (global->paths + curRouteNodeOffset);    do    {      if ( !skipForbidden || !((curRouteNode->flags >> 5) & 1) )      {        if ( !flag2 || !((curRouteNode->flags >> 6) & 1) )        {          if ( !flag3 || !((curRouteNode->field_11 >> 2) & 1) )          {            if ( flag4 == (curRouteNode->field_11 & 1) )            {              curRouteNodeY = *(&global->paths[0]._y + curRouteNodeOffset) * f8Divider;              if ( curRouteNodeY - VfY < f0 )                v3 = curRouteNodeY - VfY;              else                v3 = -(curRouteNodeY - VfY);              yOffset = v3;              curRouteNodeX = *(&global->paths[0]._x + curRouteNodeOffset) * f8Divider;              v21 = curRouteNodeX - x;              xOffset = v21;              if ( v21 >= f0 )                xOffset = -v21;              curRouteNodeZOffset = *(&global->paths[0]._z + curRouteNodeOffset) * f8Divider - z;              if ( curRouteNodeZOffset < f0 )                zOffset = curRouteNodeZOffset;              else                zOffset = -curRouteNodeZOffset;              v26 = xOffset + yOffset + f3 * zOffset;              if ( v26 >= v2 )              {                v2 = v26;                v12 = _curObjecttypetIndex;              }            }          }        }      }      ++_curObjecttypetIndex;      ++curRouteNode;      curRouteNodeOffset += 20;    }    while ( _curObjecttypetIndex < LastObjecttypeIndex );  }  if ( v2 < searchRadius )    result = -1;  else    result = v12;  return result; }

Anyone could give a suggestion to do those hacks?

This post has been edited by Swoorup on Friday, Mar 9 2012, 04:49

[DK22Pac]

QUOTE

The solution to this may be redirecting every function that accesses this struct. But that would of course take a very long time.

Yeah, you know how to do this
Possibly you need to change this full struct (as you need to increase it size).
I had same problem with SA, where TextDrawer.textureID has 2 bytes

This post has been edited by DK22Pac on Friday, Mar 9 2012, 07:55

[Deji]

EDIT: Failed to notice this is the GTA3/VC topic.

Do you have any documentation on CPathFind, then? What is GlobalMap supposed to be?

CODE

00000000 CVehicle        struc; (sizeof=0x5A0) 00000000 __physical      CPhysical ? 00000138 vehicleData     db 588 dup(?) 00000384 pVehicleHandling dd ? 00000388 pPlaneHandling  dd ? 0000038C dwHandlingFlags dd ? 00000390 m_CCarCtrl      CCarCtrl ?  (probably not CCarCtrl, thats just a temp name I gave it)

CODE

00000000 CCarCtrl        struc; (sizeof=0x38) 00000000 field_0         dd ?                  ; offset 00000004 field_4         dd ? 00000008 field_8         dw ? 0000000A                 db ?; undefined 0000000B                 db ?; undefined 0000000C field_C         dd ? 00000010 field_10        dd ? 00000014 currentPathPointIndex dw ? 00000016 nextPathPointIndex dw ? 00000018 previousPathPointIndex dw ? 0000001A field_1A        dw ? 0000001C dwLastMissionStartTime dd ? 00000020 ?dwDrivingTime  dd ? 00000024 field_24        db ? 00000025 field_25        db ? 00000026 field_26        db ? 00000027 field_27        db ? 00000028 field_28        db ? 00000029 drivingStyle    db ? 0000002A mission         db ? 0000002B action          db ? 0000002C actionFinishTime dd ? 00000030 field_30        dd ? 00000034 field_34        dd ? 00000038 CCarCtrl        ends

The annoying thing is that many functions access word values as dwords, which makes it really confusing to decompile.

This post has been edited by Deji on Monday, Apr 2 2012, 20:12

[Swoorup]

Pic from GTA SOL.

Isnt this beautiful? Only Peds path work though and liberty city is very high up north of Vice city

This post has been edited by Swoorup on Friday, Mar 9 2012, 17:56

[DK22Pac]

GTA3, some procedure which selects colors for vehicle materials. I think Ive named all stuff ~correctly, but I still can't understand how vehicle materials render process works in general

CODE

unsigned __int8 __thiscall SetVehicleColour__17CVehicleModelInfoFUcU(CVehicleModelInfo *CVehicleModelInfo, unsigned __int8 color1ID, unsigned __int8 color2ID) {  CVehicleModelInfo *vehModel; // ebp@1  char green; // bl@2  int texture; // edi@2  RpMaterial **pMaterial; // esi@2  RpMaterial *material; // ecx@8  unsigned __int8 result; // al@10  char green2; // bl@11  int texture2; // edi@11  int pMaterial2; // esi@11  RpMaterial *material2; // edx@17  char blue; // [sp+0h] [bp-28h]@2  char blue2; // [sp+4h] [bp-24h]@11  char red; // [sp+14h] [bp-14h]@2  char red2; // [sp+14h] [bp-14h]@11  vehModel = CVehicleModelInfo;  if ( color1ID != CVehicleModelInfo->renderColor1 )  {    texture = carColorTexture[color1ID];    pMaterial = &CVehicleModelInfo->color1material;    red = carcols_red[4 * color1ID];    green = carcols_green[4 * color1ID];    blue = carcols_blue[4 * color1ID];    while ( 1 )    {      material = *pMaterial;      if ( !*pMaterial )        break;      if ( material->texture && *(material->texture + 0x10) != '@' )      {        material->color.red = red;        (*pMaterial)->color.green = green;        (*pMaterial)->color.blue = blue;      }      else      {        RpMaterialSetTexture(material, texture);      }      ++pMaterial;    }    vehModel->renderColor1 = color1ID;  }  result = color2ID;  if ( color2ID != vehModel->renderColor2 )  {    pMaterial2 = &vehModel->color2material;    red2 = carcols_red[4 * color2ID];    texture2 = carColorTexture[color2ID];    green2 = carcols_green[4 * color2ID];    blue2 = carcols_blue[4 * color2ID];    while ( 1 )    {      material2 = *pMaterial2;      if ( !*pMaterial2 )        break;      if ( material2->texture && *(material2->texture + 0x10) != '@' )      {        material2->color.red = red2;        *(*pMaterial2 + 5) = green2;        *(*pMaterial2 + 6) = blue2;      }      else      {        RpMaterialSetTexture(material2, texture2);      }      pMaterial2 += 4;    }    result = color2ID;    vehModel->renderColor2 = color2ID;  }  return result; }

[maxorator]

GTA3/VC creates a list of materials that use the primary colour and a list of materials that use the secondary colour. Before a vehicle is rendered, it calls that function to change the colour of those materials to the colours of that specific car.

In VC, the function is a bit simpler, because it doesn't change the texture:

CODE

void CVehicleModelInfo::SetVehicleColour(unsigned char uPrimaryColour, unsigned char uSecondaryColour) {    if(uPrimaryColour != this->uLastPrimaryColour){        for(int i = 0; this->pPriColourMaterials[i]; i++) {            this->pPriColourMaterials[i]->rgbColour.cRed = stCarCol.rgbColours[uPrimaryColour].cRed;            this->pPriColourMaterials[i]->rgbColour.cGreen = stCarCol.rgbColours[uPrimaryColour].cRed;            this->pPriColourMaterials[i]->rgbColour.cBlue = stCarCol.rgbColours[uPrimaryColour].cRed;        }                this->uLastPrimaryColour = uPrimaryColour;    }    if(nSecondaryColour != this->uLastSecondaryColour) {        for(int i = 0; this->pSecColourMaterials[i]; i++) {            this->pSecColourMaterials[i]->rgbColour.cRed = stCarCol.rgbColours[uSecondaryColour].cRed;            this->pSecColourMaterials[i]->rgbColour.cGreen = stCarCol.rgbColours[uSecondaryColour].cGreen;            this->pSecColourMaterials[i]->rgbColour.cBlue = stCarCol.rgbColours[uSecondaryColour].cBlue;        }                this->uLastSecondaryColour = uSecondaryColour;    } }

This post has been edited by maxorator on Saturday, Apr 7 2012, 11:31

[Swoorup]

A 10 pages ago, I saw Modelling Man's post about changing an exe into a DLL. Is it any easier?

http://keeper.lubie.org/other_docs/change_exe_to_dll.htm

[Swoorup]

EDIT:

This post has been edited by Swoorup on Sunday, Jun 3 2012, 12:22

[Swoorup]

But I still couldn't get my custom grids connected. I relooked at the VC paths function to increase the path data index which is originally 2 bytes in size. There are also some bitwise operations in it, and couldn't understand what were they doing there. The 2 leftmost bits are used for somethings else, whereas the rest bits are used for indexing the paths.

[NewportByChrysler]

Would anybody know the address for the headlight flares in the GTA3 .exe?

[DK22Pac]

GTA3 1.0

CODE

0x5197A0 CBrightLights::CleanNumOfBrightLights() 0x5197B0 CBrightLights::Render() 0x51A3B0 CBrightLights::RenderOne() 0x51A410 CBrightLights::RegisterOne(float x1, float y1, float z1, float x2, float y2, float z2, float x3, float y3, float z3, float x4, float y4, float z4, char red, char green, char blue, char alpha) 0x8F2C70 NumBrightLights 0x733A68 aBrightLights    CBrightLight[32] CBrightLight    struc; (sizeof=0x38) 0x00 pointAA         RwV3D 0x0C pointAB         RwV3D 0x18 pointBA         RwV3D 0x24 pointBB         RwV3D 0x30 distanceToCamera dd 0x34 color           RwRGBA

Vice 1.0

CODE

0x5719B0 CBrightLights::Render() 0x571820 CBrightLights::RegisterOne(float x1, float y1, float z1, float x2, float y2, float z2, float x3, float y3, float z3, float x4, float y4, float z4, char red, char green, char blue, char alpha) 0x97F2BC NumBrightLights 0x818848 aBrightLights    CBrightLight[32] The struct is same.

This post has been edited by DK22Pac on Sunday, May 6 2012, 09:03

[maxorator]

The CBrightLights class is actually just the rectangular boxes near the lights, they don't affect the actual light coming out. They do, however, make the lights seem a bit more realistic as without them there would be the light, but the source of the light would look rather dark, which makes no sense. In SA this is done differently, by actually changing the texture of lights to a lighter texture. If you want to affect the actual light coming out, then you should look into CCoronas and CPointLights classes. It is also possible that some of the surface lighting (ground in front of the lights) is handled internally as shadows.

[DK22Pac]

Yeah. In SA, also, some material settings are changed (as I remember, "material diffuse" value).
This bright light is really weird thing for me. After I removed them, vehicles look better at night.
I thought about making new headlight coronas for GTAIII, since I dont like that light line.
Also, about pointligths, in SA, for vehicle lights they are really "direct lights". And it's a cool thing. But it affects only dynamic stuff, like peds and vehicles...
And about "surface lighting", like you called it, it creates 3d prim based on nearest entities' vertices. For SA, I documented CShadows struct here. Just one bad thing - these shadows could be created only on the ground, only ped shadows are drawed on the walls.

[maxorator]

Yeah, actually it will be a feature in the next version of my vehicle loader to disable the light boxes either separately for new vehicles or globally.

By the way, maybe you should also add all of that to the English GTAModding wiki.

[juarez]

Version 1.0

sub_5427A0 -> CCoronas__addCorona
sub_43D910 -> _?pickupTaken
sub_42EDE0 -> ShowGarageText
sub_42F2B0 -> DrawGarageText

//draw text above clothes and bigdollar pickups
sub_43E5E0 -> _?DrawPickupText

This post has been edited by juarez on Sunday, May 27 2012, 11:27

[JACK JONES]

Hi. I found these recently:
gta3 v1.0:

CODE

0x4C1E99 - COP weapon model - default value 2 0x4C1200 - COP pistol - default value 2 0x4C1234 - COP weapon accuracy - default value 60 0x4C125F - SWAT uzi - default value 3 0x4C126A - SWAT weapon model load - default value 3 0x4C124F - SWAT pistol - default value 2 0x4C1293 - SWAT weapon accuracy - default value 68 0x4C12BE - FBI AK47 - default value 5 0x4C12C9 - FBI weapon model load - default value 5 0x4C12AE - FBI pistol - default value 2 0x4C12F2 - FBI weapon accuracy - default value 76 0x4C131A - ARMY M16 - default value 6 0x4C1332 - ARMY weapon model load - default value 6 0x4C130A - ARMY pistol - default value 2 0x4C135B - Army weapon accuracy - default value 84

Accuracy values from 0 to 100.
Weapon values from 0 to 11:

CODE

0 - unarmed 1 - bat 2 - pistol 3 - uzi 4 - shotgun 5 - AK47 6 - M16 7 - sniper 8 - rocket launcher 9 - flamethrower 10 -molotov coctail 11 -bomb

NOTE: Wanted level personel don't know how to use sniper and rocketlauncher - they just punching you in the face with these two guns - that's too bad. However they know everything else - even a molotov or a bomb. Also I have no idea how to change both primary and secondary weapon of these peds because for example when I change FBI AK47 to M16 - the only way to change FBI pistol is to M16 because I found only one address for a weapon model for every wanted level ped - so I got a strange feeling that something is missing here.
Also I was bored so I found the same for the v1.1:

CODE

0x4C12F0 - COP pistol 0x4C1F39 - COP pistol model 0x4C1324 - COP weapon accuracy (60) 0x4C134F - SWAT uzi 0x4C135A - SWAT weapon model 0x4C133F - SWAT pistol 0x4C1383 - SWAT weapon accuracy (68) 0x4C13AE - FBI AK47 0x4C13B9 - FBI weapon model 0x4C139E - FBI pistol 0x4C13E2 - FBI weapon accuracy (76) 0x4C140A - Army M16 0x4C1422 - Army weapon model 0x4C13FA - Army pistol 0x4C144B - Army weapon accuracy (84)

[MW_29]

QUOTE (JACK JONES @ Thursday, Jun 7 2012, 04:17)

Hi. I found these recently: gta3 v1.0: CODE 0x4C1E99 - COP weapon model - default value 2 0x4C1200 - COP pistol - default value 2 0x4C1234 - COP weapon accuracy - default value 60 0x4C125F - SWAT uzi - default value 3 0x4C126A - SWAT weapon model load - default value 3 0x4C124F - SWAT pistol - default value 2 0x4C1293 - SWAT weapon accuracy - default value 68 0x4C12BE - FBI AK47 - default value 5 0x4C12C9 - FBI weapon model load - default value 5 0x4C12AE - FBI pistol - default value 2 0x4C12F2 - FBI weapon accuracy - default value 76 0x4C131A - ARMY M16 - default value 6 0x4C1332 - ARMY weapon model load - default value 6 0x4C130A - ARMY pistol - default value 2 0x4C135B - Army weapon accuracy - default value 84 Accuracy values from 0 to 100. Weapon values from 0 to 11: CODE 0 - unarmed 1 - bat 2 - pistol 3 - uzi 4 - shotgun 5 - AK47 6 - M16 7 - sniper 8 - rocket launcher 9 - flamethrower 10 -molotov coctail 11 -bomb NOTE: Wanted level personel don't know how to use sniper and rocketlauncher - they just punching you in the face with these two guns - that's too bad. However they know everything else - even a molotov or a bomb. Also I have no idea how to change both primary and secondary weapon of these peds because for example when I change FBI AK47 to M16 - the only way to change FBI pistol is to M16 because I found only one address for a weapon model for every wanted level ped - so I got a strange feeling that something is missing here. Also I was bored so I found the same for the v1.1: CODE 0x4C12F0 - COP pistol 0x4C1F39 - COP pistol model 0x4C1324 - COP weapon accuracy (60) 0x4C134F - SWAT uzi 0x4C135A - SWAT weapon model 0x4C133F - SWAT pistol 0x4C1383 - SWAT weapon accuracy (68) 0x4C13AE - FBI AK47 0x4C13B9 - FBI weapon model 0x4C139E - FBI pistol 0x4C13E2 - FBI weapon accuracy (76) 0x4C140A - Army M16 0x4C1422 - Army weapon model 0x4C13FA - Army pistol 0x4C144B - Army weapon accuracy (84)

Useful findings. If You have a time, then maybe try to find similar things for VC

...by the way, have anyone so far found memory address for color of this GREEN MENU SELECTOR rectangle???

[NewportByChrysler]

So, through memory editing, would it be possible to re-enable headlight coronas in GTAIII?

[MW_29]

QUOTE (NewportByChrysler @ Friday, Jun 8 2012, 22:44)

So, through memory editing, would it be possible to re-enable headlight coronas in GTAIII?

Well, as guys previously posted here, i assume it could be done. Maybe then it 'd be worth releasing this as official mod, not only pieces of code in this topic, i mean Anyways, keep up