Client with particles

Quote:

---

Originally Posted by RiiPiiNFtW [Only registered and activated users can see links. Click Here To Register...]

Fun fact. This doesn't support resizing particles with clients that handle zooming in and out. It also doesn't support repositioning the particles while changing between screen modes (E.G: Fixed, Resize, and Fullscreen) though it is a super easy fix if you look hard enough.

Worked with zion on a cheaphax fix for the resizing while zooming in and out too, but still gotta modify it.

Also, the origin point of the particles on the vertex doesn't stick right to the models right while on hills. Something else to look into.

---

Because person who made it didn't take account into clients fov.

Edit:
Since some people said that particles don't scale to your screen size, it's easy fixable. If you look at model renderer you see this code

Code:

---

                        if (i8 >= 50) {
                                vertexPerspectiveX[j7] = l5 + (k7 << Client.log_view_dist) / i8;// Here
                                vertexPerspectiveY[j7] = j6 + (l7 << Client.log_view_dist) / i8;// Here
                        } else {
                                vertexPerspectiveX[j7] = -5000;
                                flag = true;
                        }

---

This client * 1024 if you're on resizable mode(which is dumb, just multiply by your client width god damn, and you'll have proper FOV). I looked at draw particle method and found this

Code:

---

public final int[] writeParticlePos(int var1, int var2, int var3) {
                if (var1 >= 128 && var3 >= 128 && var1 <= 13056 && var3 <= 13056) {
                        int var6 = method42(plane, var3, var1) - var2;
                        var1 -= xCameraPos;
                        var6 -= zCameraPos;
                        var3 -= yCameraPos;
                        int var7 = Model.SINE[yCameraCurve];
                        int var8 = Model.COSINE[yCameraCurve];
                        int var9 = Model.SINE[xCameraCurve];
                        int var10 = Model.COSINE[xCameraCurve];
                        int var11 = var3 * var9 + var1 * var10 >> 16;
                        var3 = var3 * var10 - var1 * var9 >> 16;
                        var1 = var11;
                        var11 = var6 * var8 - var3 * var7 >> 16;
                        var3 = var6 * var7 + var3 * var8 >> 16;
                        return var3 >= 50 && var3 <= 3500 ? new int[] { Rasterizer.centerX + (var1 << 9) / var3, Rasterizer.centerY + (var11 << 9) / var3, var3, Rasterizer.centerX + (var1 / 2 << 9) / var3, Rasterizer.centerY + (var11 / 2 << 9) / var3, Rasterizer.centerX + (var1 / 2 << 9) / var3, Rasterizer.centerY + (var11 / 2 << 9) / var3 }

                                        : new int[] { 0, 0, 0, 0, 0, 0, 0 };
                } else {
                        return new int[] { 0, 0, 0, 0, 0, 0, 0 };
                }
        }

---

This still have << 9, we replace it with

Code:

---

        public final int[] writeParticlePos(int var1, int var2, int var3) {
                if (var1 >= 128 && var3 >= 128 && var1 <= 13056 && var3 <= 13056) {
                        int var6 = method42(plane, var3, var1) - var2;
                        var1 -= xCameraPos;
                        var6 -= zCameraPos;
                        var3 -= yCameraPos;
                        int var7 = Model.SINE[yCameraCurve];
                        int var8 = Model.COSINE[yCameraCurve];
                        int var9 = Model.SINE[xCameraCurve];
                        int var10 = Model.COSINE[xCameraCurve];
                        int var11 = var3 * var9 + var1 * var10 >> 16;
                        var3 = var3 * var10 - var1 * var9 >> 16;
                        var1 = var11;
                        var11 = var6 * var8 - var3 * var7 >> 16;
                        var3 = var6 * var7 + var3 * var8 >> 16;
                        return var3 >= 50 && var3 <= 3500 ? new int[] { Rasterizer.centerX + (var1 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 << Client.log_view_dist) / var3, var3, Rasterizer.centerX + (var1 / 2 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 / 2 << Client.log_view_dist) / var3, Rasterizer.centerX + (var1 / 2 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 / 2 << Client.log_view_dist) / var3 }

                                        : new int[] { 0, 0, 0, 0, 0, 0, 0 };
                } else {
                        return new int[] { 0, 0, 0, 0, 0, 0, 0 };
                }
        }

---

And look particles scale to your client size!

[Only registered and activated users can see links. Click Here To Register...]


P.S please use your client width instead of fixed numbers like 2^9 and 2^10

Quote:

---

Originally Posted by Leanbow [Only registered and activated users can see links. Click Here To Register...]

Because person who made it didn't take account into clients fov.

Edit:
Since some people said that particles don't scale to your screen size, it's easy fixable. If you look at model renderer you see this code

Code:

---

                        if (i8 >= 50) {
                                vertexPerspectiveX[j7] = l5 + (k7 << Client.log_view_dist) / i8;// Here
                                vertexPerspectiveY[j7] = j6 + (l7 << Client.log_view_dist) / i8;// Here
                        } else {
                                vertexPerspectiveX[j7] = -5000;
                                flag = true;
                        }

---

This client * 1024 if you're on resizable mode(which is dumb, just multiply by your client width god damn, and you'll have proper FOV). I looked at draw particle method and found this

Code:

---

public final int[] writeParticlePos(int var1, int var2, int var3) {
                if (var1 >= 128 && var3 >= 128 && var1 <= 13056 && var3 <= 13056) {
                        int var6 = method42(plane, var3, var1) - var2;
                        var1 -= xCameraPos;
                        var6 -= zCameraPos;
                        var3 -= yCameraPos;
                        int var7 = Model.SINE[yCameraCurve];
                        int var8 = Model.COSINE[yCameraCurve];
                        int var9 = Model.SINE[xCameraCurve];
                        int var10 = Model.COSINE[xCameraCurve];
                        int var11 = var3 * var9 + var1 * var10 >> 16;
                        var3 = var3 * var10 - var1 * var9 >> 16;
                        var1 = var11;
                        var11 = var6 * var8 - var3 * var7 >> 16;
                        var3 = var6 * var7 + var3 * var8 >> 16;
                        return var3 >= 50 && var3 <= 3500 ? new int[] { Rasterizer.centerX + (var1 << 9) / var3, Rasterizer.centerY + (var11 << 9) / var3, var3, Rasterizer.centerX + (var1 / 2 << 9) / var3, Rasterizer.centerY + (var11 / 2 << 9) / var3, Rasterizer.centerX + (var1 / 2 << 9) / var3, Rasterizer.centerY + (var11 / 2 << 9) / var3 }

                                        : new int[] { 0, 0, 0, 0, 0, 0, 0 };
                } else {
                        return new int[] { 0, 0, 0, 0, 0, 0, 0 };
                }
        }

---

This still have << 9, we replace it with

Code:

---

        public final int[] writeParticlePos(int var1, int var2, int var3) {
                if (var1 >= 128 && var3 >= 128 && var1 <= 13056 && var3 <= 13056) {
                        int var6 = method42(plane, var3, var1) - var2;
                        var1 -= xCameraPos;
                        var6 -= zCameraPos;
                        var3 -= yCameraPos;
                        int var7 = Model.SINE[yCameraCurve];
                        int var8 = Model.COSINE[yCameraCurve];
                        int var9 = Model.SINE[xCameraCurve];
                        int var10 = Model.COSINE[xCameraCurve];
                        int var11 = var3 * var9 + var1 * var10 >> 16;
                        var3 = var3 * var10 - var1 * var9 >> 16;
                        var1 = var11;
                        var11 = var6 * var8 - var3 * var7 >> 16;
                        var3 = var6 * var7 + var3 * var8 >> 16;
                        return var3 >= 50 && var3 <= 3500 ? new int[] { Rasterizer.centerX + (var1 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 << Client.log_view_dist) / var3, var3, Rasterizer.centerX + (var1 / 2 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 / 2 << Client.log_view_dist) / var3, Rasterizer.centerX + (var1 / 2 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 / 2 << Client.log_view_dist) / var3 }

                                        : new int[] { 0, 0, 0, 0, 0, 0, 0 };
                } else {
                        return new int[] { 0, 0, 0, 0, 0, 0, 0 };
                }
        }

---

And look particles scale to your client size!

[Only registered and activated users can see links. Click Here To Register...]


P.S please use your client width instead of fixed numbers like 2^9 and 2^10

---

I already mentioned that fix at the bottom of the second page, I just didn't spoon feed as much :P

Quote:

---

Originally Posted by Stevenhax [Only registered and activated users can see links. Click Here To Register...]

Got mine working a moment ago, where I went wrong was at RenderAtPoint in model.java where the parameters on his copy didn't match mine so I was
setting offX Y Z wrong. Thought I'd mention it in case you overlooked that as well.

---

Thank you for mentioning renderAtPoint I forgot to add something in there to make it work.
This is what it looks like right now:
[Only registered and activated users can see links. Click Here To Register...]
I think I have to increase the density a bit.

Quote:

---

Originally Posted by Leanbow [Only registered and activated users can see links. Click Here To Register...]

Because person who made it didn't take account into clients fov.

Edit:
Since some people said that particles don't scale to your screen size, it's easy fixable. If you look at model renderer you see this code

Code:

---

                        if (i8 >= 50) {
                                vertexPerspectiveX[j7] = l5 + (k7 << Client.log_view_dist) / i8;// Here
                                vertexPerspectiveY[j7] = j6 + (l7 << Client.log_view_dist) / i8;// Here
                        } else {
                                vertexPerspectiveX[j7] = -5000;
                                flag = true;
                        }

---

This client * 1024 if you're on resizable mode(which is dumb, just multiply by your client width god damn, and you'll have proper FOV). I looked at draw particle method and found this

Code:

---

public final int[] writeParticlePos(int var1, int var2, int var3) {
                if (var1 >= 128 && var3 >= 128 && var1 <= 13056 && var3 <= 13056) {
                        int var6 = method42(plane, var3, var1) - var2;
                        var1 -= xCameraPos;
                        var6 -= zCameraPos;
                        var3 -= yCameraPos;
                        int var7 = Model.SINE[yCameraCurve];
                        int var8 = Model.COSINE[yCameraCurve];
                        int var9 = Model.SINE[xCameraCurve];
                        int var10 = Model.COSINE[xCameraCurve];
                        int var11 = var3 * var9 + var1 * var10 >> 16;
                        var3 = var3 * var10 - var1 * var9 >> 16;
                        var1 = var11;
                        var11 = var6 * var8 - var3 * var7 >> 16;
                        var3 = var6 * var7 + var3 * var8 >> 16;
                        return var3 >= 50 && var3 <= 3500 ? new int[] { Rasterizer.centerX + (var1 << 9) / var3, Rasterizer.centerY + (var11 << 9) / var3, var3, Rasterizer.centerX + (var1 / 2 << 9) / var3, Rasterizer.centerY + (var11 / 2 << 9) / var3, Rasterizer.centerX + (var1 / 2 << 9) / var3, Rasterizer.centerY + (var11 / 2 << 9) / var3 }

                                        : new int[] { 0, 0, 0, 0, 0, 0, 0 };
                } else {
                        return new int[] { 0, 0, 0, 0, 0, 0, 0 };
                }
        }

---

This still have << 9, we replace it with

Code:

---

        public final int[] writeParticlePos(int var1, int var2, int var3) {
                if (var1 >= 128 && var3 >= 128 && var1 <= 13056 && var3 <= 13056) {
                        int var6 = method42(plane, var3, var1) - var2;
                        var1 -= xCameraPos;
                        var6 -= zCameraPos;
                        var3 -= yCameraPos;
                        int var7 = Model.SINE[yCameraCurve];
                        int var8 = Model.COSINE[yCameraCurve];
                        int var9 = Model.SINE[xCameraCurve];
                        int var10 = Model.COSINE[xCameraCurve];
                        int var11 = var3 * var9 + var1 * var10 >> 16;
                        var3 = var3 * var10 - var1 * var9 >> 16;
                        var1 = var11;
                        var11 = var6 * var8 - var3 * var7 >> 16;
                        var3 = var6 * var7 + var3 * var8 >> 16;
                        return var3 >= 50 && var3 <= 3500 ? new int[] { Rasterizer.centerX + (var1 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 << Client.log_view_dist) / var3, var3, Rasterizer.centerX + (var1 / 2 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 / 2 << Client.log_view_dist) / var3, Rasterizer.centerX + (var1 / 2 << Client.log_view_dist) / var3, Rasterizer.centerY + (var11 / 2 << Client.log_view_dist) / var3 }

                                        : new int[] { 0, 0, 0, 0, 0, 0, 0 };
                } else {
                        return new int[] { 0, 0, 0, 0, 0, 0, 0 };
                }
        }

---

And look particles scale to your client size!

[Only registered and activated users can see links. Click Here To Register...]


P.S please use your client width instead of fixed numbers like 2^9 and 2^10

---

Yea figured this part out. Haven't properly figured out resizing while zooming in and out though. Still tinkering with the numbers. Sure there is a better way to handle it.

Quote:

---

Originally Posted by Leanbow [Only registered and activated users can see links. Click Here To Register...]

Because person who made it didn't take account into clients fov.

---

Quote:

---

Originally Posted by RiiPiiNFtW [Only registered and activated users can see links. Click Here To Register...]

Yea figured this part out. Haven't properly figured out resizing while zooming in and out though. Still tinkering with the numbers. Sure there is a better way to handle it.

---

RiiPiiNFtW, This will fix the resizing for you.

Code:

---

public int[] projection(int i, int j, int l, int width, int height) {
        if (i < 128 || l < 128 || i > 13056 || l > 13056) {
            return new int[]{0, 0, 0, 0, 0, 0, 0};
        }
        int i1 = method42(plane, l, i) - j;
        i -= xCameraPos;
        i1 -= zCameraPos;
        l -= yCameraPos;
        int j1 = Model.modelIntArray1[yCameraCurve];
        int k1 = Model.modelIntArray2[yCameraCurve];
        int l1 = Model.modelIntArray1[xCameraCurve];
        int i2 = Model.modelIntArray2[xCameraCurve];
        int j2 = l * l1 + i * i2 >> 16;
        l = l * i2 - i * l1 >> 16;
        i = j2;
        j2 = i1 * k1 - l * j1 >> 16;
        l = i1 * j1 + l * k1 >> 16;
        i1 = j2;
        if (l >= 50 && l <= 3500) {
            return new int[]{Texture.textureInt1 + (i << log_view_dist) / l, Texture.textureInt2 + (i1 << log_view_dist) / l, l, Texture.textureInt1 + ((i - (width / 2)) << log_view_dist) / l, Texture.textureInt2 + ((i1 - (height / 2)) << log_view_dist) / l, Texture.textureInt1 + ((i + (width / 2)) << log_view_dist) / l, Texture.textureInt2 + ((i1 + (height / 2)) << log_view_dist) / l};
        }
        return new int[]{0, 0, 0, 0, 0, 0, 0};


    }

---

Don't forget this!

Code:

---

                    particleCenter = projection(px, py, pz, pWidth, pHeight); //cX, cY, cD, tX, tY, bX, bY
                    pWidth = particleCenter[5] - particleCenter[3];
                    pHeight = particleCenter[6] - particleCenter[4];

---

@Leanbow,

The version on the mistex client isn't the latest version; it's much older and was ripped out of my client before that FOV hack was introduced.
Thanks.ee for letting them know what to change though.

does anybody still have this?

Quote:

---

Originally Posted by Dalethium [Only registered and activated users can see links. Click Here To Register...]

does anybody still have this?

---

Reuploaded, sorry about that.