@ikt
That untested asi got it to work great for me, (froze b4 when I pressed k) thanks for updating! ^.^

Updated for 1.0.1180.2. This is the same as the previous 2 releases, so just fixed an offset.

@ikt Use this pattern: 3C 03 0F 85 ? ? ? ? 48 8B 41 20 48 8B 88 and read the int at patternAddr + 0x16. Works for any game version.

@Unknown Modder Could you tell us a pattern that can find handling data addresses from handling hashes If you know that?
RPH has a way to find them from handling hashes, but the pattern will help everyone (including ikt and me).

@kagikn E8 ? ? ? ? 48 85 C0 75 5A B2 01 (address of the function is at: patternAddr + *(int*)(patternAddr + 1) + 5)
CHandlingData* GetHandlingDataByHash(uint32_t* hash);

@Unknown Modder
Thanks! Where/what for is this one used?

@Unknown Modder Thanks a lot, man! I'll use this pattern to implement HandlingData class in SHVDN.
Looks similar to this function btw (I tried the pattern in FiveM source code but I couldn't find the usage). https://github.com/citizenfx/fivem/blob/master/code/components/handling-loader-five/src/HandlingDataManager.cpp#L264

@ikt Do you mean the pattern or the usage internally?
@kagikn The function I posted returns the handling data pointer and the function FiveM uses returns the index. That means you would still need to loop access the handling data array to get the pointer, so I posted the function that returns the pointer directly. Btw, there is also a GetHandlingDataByIndex function directly above those two.

@Unknown Modder
The usage internally, although context for the pattern would also be nice to know. Anything that would help picking a pattern from a list the debugger found :)

@Unknown Modder I grasped what the return value of the function FiveM uses represents. Thanks for explaining it.

Great update! One day I'll understand how you guys find these stuff (hopefully) lol

@ikt I'm not sure what the function does. Haven't done any research for that yet (not enough time).

I don't know if @Unknown Modder has mentioned it or not but GetHandlingDataByHash should probably be named GetHandlingDataByHandlingNameHash instead since the handling name can be different from the model name.

If you need to get the handling data by vehicle model hash the way I can think of right now is to first get the model info by calling GetVehicleModelInfoByModelHash. Then find out the handling index inside the CVehicleModelInfo struct (offset 0x488 for 1180). Then you can call GetHandlingDataByIndex.

@uNiverselEgacy I thought it was obvious but yeah, it might be a good idea if you have another function that returns the handling data for a vehicle model.

If you are interested in implementing sub handling editing there's a convenient function CBaseSubHandlingData *GetSubHandlingDataOfType(CHandlingData *handling, int type). I also have their patterns so you can make it future proof. Also I've done some reclass work on some sub handling classes like CBikeHandlingData, CFlyingHandlingData, CBoatHandlingData, CSeaPlaneHandlingData, CSubmarineHandlingData, CTrailerHandlingData, CCarHandlingData.

@Unknown Modder well I failed to find a function that directly returns the handling data for a vehicle model but I have provided a way to write such a function above. Just tested it and it works pretty well.

@uNiverselEgacy It's similar to what I use. I have this in my CVehicleModelInfo class which is slightly faster than getting the index and then calling GetHandlingDataByIndex:
inline CHandlingData* GetHandlingData() const
{
return g_handlingDataArray[m_handlingIndex];
}

Nice mod, thank you. Works great with N++. Strongly recommended.