Trouble with DR3

[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.

[sonicintuition]

As you can see in my above post, I clearly state that I am very new to C++ coding, and reading this stuff is like a foreign language. Being new I would have no clue if the errors are something native to the EQemu code itself or something that can be fixed with outside help, therefore I did not look outside the community for assistance. Now that you've explained that to me, I will do that. Thanks for your advice.

Regards,
SI

[sysadmin]

You are in a better position than me, I do not know ANY c or c++ or VC or any other flavor. I myself have been flamed MANY times because I did not searched for the answer, or was dumb enough to not find the answer on the internet.

I simply was pointing out that WE(includes me also) should do the best in our power to find the answer before buggin a developer since they have more important things to think about and solve before answering any of mine or anyone elses noob questions.

[RangerDown]

There's no need for the personal attacks. The code that SI is reporting is worthy of investigation, since 0.5 should be a perfectly valid value for a float. The MSKB article posted does little to remedy the fact that 0.5 is a nice middle-of-the-road value for a "float" type.

What may be wrong in this case is either the compiler you're using is somehow confused or improperly set, or the actual offender is one or two lines above or below the line number you're seeing in error messages. Your compiler may, for whatever reason, have a different idea of what a "float" is than the standard data type.

If others are getting C2177's on those very lines, then something may be wrong with the code. But I've visually verified the code you pasted follows proper syntax, and since you are the only one reporting errors there, we have to assume the problem lies in the compiler you are using.

[sysadmin]

In my experience with other programming languages the same compiler led to different errors when using different hardware, aside the options used to configure the compiler.

I think the best possible solution would be to search the knowledge base at the compiler's developer site. They might have already a solution, or at least a workaround.
.