Trouble with DR3

[sonicintuition]

Greetings,

Is there anyone out there who been able to successfully compile the current CVS dump (DR3) in windows using VS.NET 2k3? I was able to compile World.exe, EQsharemem.dll, however Zone.exe will not compile, due to numerous "Constant too big" errors, 33 to be exact. I read another post regarding this issue and nobody answered the person. Then I found another post about the same thing in which FNW replied saying to make the constants smaller. I go to the lines where these errors are listed at, and find nothing that looks like it needs to be, or even should be adjusted, and certainly doesn't look like the examples FNW gave.

If anyone has been able to get around this, please tell me how it is done, OR, if anyone is willing to share a copy of the latest perl-enabled compilation of Zone.exe (DR3) please PM me. I would prefer to do my own compiling but at this point am willing to settle for someone elses.

Thanks in advance.

Regards,
SI

[sysadmin]

SEARCH BUTTON IS YOUR FRIEND

[sonicintuition]

First, that didn't help. I'm not looking for quick smart-ass replies, like "Search is your friend" because ...I did search, for a long time, and that is why I bothered to post in the first place. Second, the post you linked to does not help me.

Then I found another post about the same thing in which FNW replied saying to make the constants smaller. I go to the lines where these errors are listed at, and find nothing that looks like it needs to be, or even should be adjusted, and certainly doesn't look like the examples FNW gave.

What you linked, is what I was referring to.

The examples he shows there does not even come close to anything shown on the lines that VS.NET reports the "Constant too big" error. Being that I am not a coder, I am unable to know what needs to be changed. I have never had a problem compiling the server binaries on my own till now, and that's what I need help with.

Still requesting help with this, or anyone generous enough to donate a DR3 Zone.exe. Thanks.

Regards,
SI

[mrea]

If the post http://www.eqemulator.net/forums/sho...89&postcount=2 is what sysadmin linked it is exactly your problem. Do what it says and you'll be in good shape

[sonicintuition]

Alright, I'm going to have to post some examples. What FNW shows in that thread is NOT what I'm seeing on the lines that show as containing errors. Here are a few examples:

This is what shows in the VS.NET compiler after trying to compile. This is just ONE example of 33 errors, all are the same, "Constant too big":

c:\EQEmuCVS\Source\zone\AA.cpp(489): error C2177: constant too big

I then double click that to go right to that file and line to edit it, and find this:

aps->experience = (int32)(((float)330.0f * (float)m_pp.expAA) / (float)max_AAXP);

Not the 99999990e111 type thing that FNW is talking about. Soo...what would I edit in that line? I tried adjusting the numbers in a few of these instances but nothing changed, or errors started showing up in other files. Please note that almost all of the errors that showed up contained lines like this one, with a lot of mumbo jumbo and no large arbitrary numbers such as those described by FNW.

Here's another example:

c:\EQEmuCVS\Source\zone\aggro.cpp(896): error C2177: constant too big

Going there shows me this:

float perwalk_x = 0.5;

There are 5 lines almost exactly like this in the code surrounding that line. Why are they not pointed out like this one?

I am very new at C++ coding. The extent of my abilities include creating a hello world program in the console, and (used to be) compiling EQemu flawlessly. When I look at lines like that above though, it's a foreign language to me. I am very willing to learn, and am currently making an attempt in my spare time to work on my C++ skills, but I really need help with this.

Regards,
SI

[sysadmin]

Visual Studio Developer site says

Compiler Error C2177
constant too big

A constant value is too large for the variable type it is assigned.

The following sample generates C2177:

// C2177.cpp
int main() {
int a=18446744073709551616; // C2177
int b=18446744073709551615; // OK
}

FNW knows his stuff, I don't but I was smart to find the same answer on VS2005 website and you did not, even when you searched "for a long time". Also you should rename yourself to sonic because as I see you have no intuition.

[LethalEncounter]

If anyone is still having this problem:

1. Open client.h and find ClearAllProximities()
2. Change all the 1000e99 on that line to FLT_MAX.
3. Add #include <float.h> to the top of the file.

This should fix the vast majority of the "costant too large" messages. Any other errors should be easy to identify and fix, the reason why this instance was hard to find was because VS .Net would say the error was at a seemingly random location instead of the real location. Compounding this was the fact that about 30 files include client.h, making it seem like you had a ton of errors when it was really just one.

[RangerDown]

Thanks Lethal!!

You're dropping the Edgar1898 handle I see :(