OH WOW! JUST WOW!!!

That looks GREAT Orazio!

I would love to have some new integrated cabins in ERAS! Its actually one of the things I am working on but using modded cabins that were made for SOFS and TEHO with new textures from some of the Corsairs Harbor modders.

So my plan was instead of making a whole new category of cabins, to simply…[Read more]

Jeffrey you are the MAN!!!!

YOU DID IT!!!!!!!!!!!!!

This really makes my whole week! Thank you!

This is an AMAZING additional capability that players are really going to enjoy. It completely changes the usual mechanics. I can’t wait to go into some of the quest battles where you usually end up alone or maybe with one really good fighter left.…[Read more]

Jeffrey you are the MAN!!!!

YOU DID IT!!!!!!!!!!!!!

This really makes my whole week! Thank you!

This is an AMAZING additional capability that players are really going to enjoy. It completely changes the usual mechanics. I can’t wait to go into some of the quest battles where you usually end up alone or maybe with one really good fighter left.…[Read more]

Jeffrey you are the MAN!!!!

YOU DID IT!!!!!!!!!!!!!

This really makes my whole week! Thank you!

This is an AMAZING additional capability that players are really going to enjoy. It completely changes the usual mechanics. I can’t wait to go into some of the quest battles where you usually end up alone or maybe with one really good fighter left.…[Read more]

I think I found it in XInterface. I put a note for myself to investigate:

memcpy(&m_screenSize,&ScreenSize,sizeof(ScreenSize));
memcpy(&m_hostRect,&hostRect,sizeof(hostRect));

//TO DO: Trace this logic to see about keeping background stretched for position = 0,0,800,600, but adjusting
// x pos for all other rectangles to NOT…[Read more]

I think I found it in XInterface. I put a not for myself to investigate:

memcpy(&m_screenSize,&ScreenSize,sizeof(ScreenSize));
memcpy(&m_hostRect,&hostRect,sizeof(hostRect));

//TO DO: Trace this logic to see about keeping background stretched for position = 0,0,800,600, but adjusting
// x pos for all other rectangles to NOT…[Read more]

I think I found it in XInterface. I put a not for myself to investigate:

memcpy(&m_screenSize,&ScreenSize,sizeof(ScreenSize));
memcpy(&m_hostRect,&hostRect,sizeof(hostRect));

//TO DO: Trace this logic to see about keeping background stretched for position = 0,0,800,600, but adjusting
// x pos for all other rectangles to NOT stretch other…[Read more]

I think I found it in XInterface. I put a not for myself to investigate:

memcpy(&m_screenSize,&ScreenSize,sizeof(ScreenSize));
memcpy(&m_hostRect,&hostRect,sizeof(hostRect));

//TO DO: Trace this logic to see about keeping background stretched for position = 0,0,800,600, but adjusting
// x pos for all other rectangles to NOT stretch other…[Read more]

Thinking about this more, I realized I was probably wrong in how it was done. I don’t have the benefit of a wider screen to review, but it makes sense it would have to stretch those screens in wide aspect ratios, else the screen would left-align, then a bunch of empty space on the right. I’m guessing you don’t see that in stock AoP, right?

So…[Read more]

I don’t think programming is needed. It looks like that is all done in the character INI file. For demonstration, I changed a few values in RESOURCEINIinterfacescharacter_all.ini to shift some things over:

You can move, resize, change font size, etc. It’s involved, but everything on the screen can be modified in that file. Don’t change…[Read more]

To MK: I read your thread “request for modeling help”, but I didn’t write anything because at the time I had just started, and could really not help. Even now, I don’t think I can help, I’m still inexperienced and before accepting tasks from other people, I want to be sure I am able to fulfill them.

I read that too, and didn’t respond for the s…[Read more]

There was an issue with no loader screens displaying pictures, as the code had deprecated use of the FADER_PICTURE message, and replaced it with FADER_DATA. But that also uses an object property setting for the image name/path. I liked the idea as it obviates the need for long “lssffllss” type parameters with the corresponding parm list; you…[Read more]

There was an issue with no loader screens displaying pictures, as the code had deprecated use of the FADER_PICTURE message, and replaced it with FADER_DATA. But that also uses an object property setting for the image name/path. I liked the idea as it obviates the need for long “lssffllss” type parameters with the corresponding parm list; you…[Read more]

Ha! Downloaded the archived version of 4.44 FMOD Ex API, fixed up the SoundService.cpp a little bit to deal with the inc/lib/dll that came with it, and my sound is back.

Told ya it was the battle_interface.dll. Increased the MAX_MAN_QUANTITY, recompiled the .dll.

Not sure why they don’t all line up…but my job of proving it was the .dll, is done.

A few problems to work through…but a saved game loaded:

Still a bunch of invalid function calls needs resolving…
RUNTIME ERROR - file: seadogs.c; line: 307
Invalid function call
RUNTIME ERROR - file: sea_aiAIShip.c; line: 4132
Invalid function call
RUNTIME ERROR - file: sea_aiAIShip.c; line: 4132
function 'SetTextureForShip' stack…[Read more]

A few problems to work through…but a saved game loaded:

Still a bunch of invalid function calls needs resolving…
RUNTIME ERROR - file: seadogs.c; line: 307
Invalid function call
RUNTIME ERROR - file: sea_aiAIShip.c; line: 4132
Invalid function call
RUNTIME ERROR - file: sea_aiAIShip.c; line: 4132
function 'SetTextureForShip' stack…[Read more]

Compiles successfully and runs from source:

Stepping through debug mode, figured out that zero parameter thing was that they are extern now, rather native. Change that in the run-time files in the Program folder and that went away, along with the erroneous duplicate variable thing (probably confused by the other problem and just erroneous…[Read more]

Ah, what the heck…curiosity got the best of me, so I’m debugging the parser.

Truncated seadogs.c to this:

native int SetGlowParams(float fBlurBrushSize, int Intensivity, int BlurPasses);

void Main()
{
SetGlowParams(1.0, 50, 2);
}

Got the same error.log, but with only 6 lines, quick/easy to step through.

In compiler.cpp, get to this line:…[Read more]

Well, well…

Just for grins, I created a C++ project folder and copied over the fresh, unadulterated source for the game I have. It didn’t compile. But the errors were relatively simple (though a bit time consuming 🙂 ) to rectify, without modifying the source code. I was missing some static libraries for FMOD, some references to static…[Read more]