Printable View
Why do all caches have a salted index and a normal index for their instances instead of just a normal index? I just noticed that the first two letters of the DataHeader name is ORed with 0x8000 as the first salted index, then increased from there. Thought it was kinda cool, but can figure out why Kornman!
The vista side of my macbook went kaput after almost 34 months of use. However, since I can run OSX fine, I don't think it's hardware related (unless OSX is just THAT awesome...hmmmm).
So yeah, until I get an alternative dev environment up, all endeavors of mine are down for the count. Expect designing. Don't need windows to design new things. Just the code development part heh.
I guess it's fitting, since I'm moving next week and need to pack anyway vOv
Man, that sucks. Good luck with the move and hope things will get back to normal for ya :downs:
On another note, while reversing a function, I was referencing off your object definition struct for offsets and found a minor struct error. Your object_header_block_reference struct is backwards, the size is first and offset is second.
Example of it being used in CE 1.08:
Which is object_data.NodeMatrixBlock.Offset into edx, then object_data + offset.Code:004F9D22 MOVSX EDX,WORD PTR DS:[EBX+1F2]
...
004F9D33 ADD EDX,EBX
If you go to the address put in edx, it's the matrix block. If you highlight the matrix block, it adds up to the size at object_data + 0x1F0. So, just thought you might know in case you ever go to use it.
E: Also, do you have node matrix definition in OS? I can't seem to find it. I know that it's always 13 floats: first float is usually, if not always 1.0f, the next 9 floats are unit vectors, and the last 3 floats are node world position. This is an unusual matrix, do you have any information on it?
Found a bug, although you've probably already fixed it, but here it is just in case.
In YeloSettings.cpp the LoadSettingsUser function doesn't close the file that it opens, which stops any settings from being saved later on. Also, in some of your components' LoadSettings functions you have "int32 i" being declared inside the if statement that reads from the settings file, which results in the component always loading default settings.
Also, in Main.cpp the Settings component is initialised and loads all settings first, but should to settings not be loaded last? As currently it loads the settings of other components, which are then initialised afterwards, plausibly reverting any loaded values to defaults.Code:int32 i = 0;
if (file != NULL && fscanf_s(file, "[FOV]\n") != EOF)
{
int32 i = fscanf_s(file, "vertical radians: %f\n", &_fov_globals.fov.vertical);
fscanf_s(file, "\n");
}
//i will always be zero
if (i < 1)
_fov_globals.InitializeToDefaultSettings();
Yeah, those were the fixes I had to apply to get the settings working. At least C# will typically inform me of silly mistakes when redeclaring variables in child blocks.
There shouldn't be any cases in my own use of the system where the settings are modified in the component's Initialize function. The settings initialization should all occur within the LoadSettings crap, even when it is just to set them to the default values.
The Initialize\Dispose system should really just be for runtime based computations. If the settings are known before the Yelo game state begins, then the initialize code can perform any game changes based on variable settings once and should treat all setting values as read only. It's not until the Yelo update state begins where it should be assumed safe to change the values of the settings.
Could a better system been created? Of course (think XML). I really just wanted to keep a very simple system in place and decided to reuse the old Battery code with some adjustments in code flow and such. Allowed more time to be spent on other things
Hey Korn before the final release of Open Sauce can you look at opening up Hud_Messages for editing in Guerilla?
What are you talking about? There is no "hud_messages" tag type, are you talking about "hud_message_text"?Quote:
Originally Posted by Dwood
Yes.Quote:
Originally Posted by ShadowSpartan
Odd, some of the fields for that tag are still locked. You can use Korn's old Guerilla, it edits that tag fine.Quote:
Originally Posted by Dwood
Thanks! I didn't think of that, sadly >.>Quote:
Originally Posted by ShadowSpartan