Welcome to the ZDoom Forums!

Thanks for the correction. Darway, Mink, Doomnobody are people's name who take the credit of the translation, and you can see the year is 2005, already long time ago. Like the people here, we are not using real names. Instead, we use catchy or English names. For "Phobos" and "Deimos", actually it is ...

For traditional Chinese, I'd like to make some fast contributions since there are existing materials for stories like E1TEXT, C2TEXT, P3TEXT, T4TEXT, which came from a group of Taiwanese players more than a decade ago.

For anyone who is interested in where they are, they're here.

Thank you for your contributions Randi. Thank you again.

Good luck.

kodi: Your ideas are correct. What makes your projection inaccurate is actually introduced by calibrating the center of your view according to the angle and pitch of the player. When you calibrated pitch, be aware that angle is changed as well. In other words, the angle of the object in player's ...

To do this, you'll need to implement 1. Get aspect ratio from wiki . Note that a kind of aspect ratio 17:10 is not mentioned on wiki. 2. Get the range of angle of player's view by FOV and aspect ratio from this thread . 3. Use pinhole camera model to project a 3D coordinate to 2D plane. Before ...

Some more tests.

#define TEST_A !2 // ACC = 0, Actual = 0
#define TEST_B ~2 // ACC = ERR, Actual = -3
#define TEST_C +2 // ACC = ERR, Actual = 2
#define TEST_D -5 // ACC = -2, Actual = -2

That would be int tid = 0; // TID of the object. int angle = GetActorAngle(tid), pitch = GetActorPitch(tid), roll = -GetActorRoll(tid); int sa = sin(angle), ca = cos(angle), sp = sin(pitch), cp = cos(pitch), sr = sin(roll), cr = cos(roll); int r11 = FixedMul(ca, cp), r12 = FixedMul(FixedMul(ca, sp ...

Looks like a: takes a character array instead of a string array. The difference is when reading them as numbers, it would be str char[4] = { "w", "h", "a", "t" } str char[4] = { 0, 1, 2, 3 } That's the index in the string table instead of the characters in the string. To correct this, use characters ...

As GooberMan's suggest, this can be something like... Script "EventLoop" (void) { switch (date) { case 20130318: switch (time) { case 0800: JackSowsBeans(); break; case 1500: ZackStealsBeans(); break; ... } case 20130319: switch (time) { case 0800: JackSowsBeansAgain(); break; ... } ... } Delay(1 ...

You could add CheckSight to make sure the light can actually be seen. Excluding something like, for example, light passing through a thin door.

Ok, this is what I have now: script 535 (void) //Flashlight Light Positioning { //NOTE THAT LARGE PORTIONS OF THIS SCRIPT WERE BORROWED FROM THE ZDOOM WIKI //http://zdoom.org/wiki/Cleaned_up_Third_Person_Cam //credit goes to the author of that page int r = MAX_R; //This is 256 int lightnum = 4 ...

GetHUDRight and GetHUDLeft finds the true location of the edge on the screen, but needs to be updated since a new aspect ratio 17:10 is introduced. Usage: Call GetHudBorders(HUDWidth, HUDHeight) then all true borders will be stored in HudLeft, HudRight, HudTop, and HudBottom variables. Function int ...

Thanks for GetActorVelocity, this is easier now. Function int GetStrafePortion(void) { int pa = GetActorAngle(0); int vx = -GetActorVelY(0), vy = GetActorVelX(0); if (!(vx | vy)) { return 0.0; } // ZDaemon version. int a = VectorAngle(vx, vy); int len; if((a + 0.125) & 0.25) { len = FixedDiv(vy, sin ...

What if there are multiple cases with the same value since it can use variables? If fact, during compile time, ACC sorts all the numbers in the case list for zdoom to perform binary search for speed. Instead, vanilla ACC doesn't sort the numbers and zdoom checks them one by one. Only the latter one ...

Just make a quick investigation about this. The number 12800 is obtained by GetPlayerInput directly. That's the base concept even the number is not correct. Ther are two different values for side move, 12800 from mouse strafing and 10240 from movement keys. The attachment can be run directly to see ...