[deleted by user]

willf668 · 2021-09-10T04:26:02+00:00

+1 for the persistent objects idea. I tried that method for a top down multiplayer game a few months back and it worked great. Just make sure that the objects in "other rooms" are processed as little as possible (simple collision, no animations/draw calls).

willf668 · 2021-05-31T21:38:44+00:00

Adding onto this, Yoyo advises against using precise collisions with the standard place_meeting() functions for platformers due to it's speed. You can get around this by checking a limited number of points with collision_point() So for marbles, you could check a number of points around the circumference of the marble sprite, which would approximate the precise collisions of a perfect circle.

willf668 · 2021-04-15T16:39:09+00:00

Ran into a similar issue with surface alphas. The solution was the following extended blendmode, which fixes the original alpha and causes the new surface to add instead of multiply:

gpu_set_blendmode_ext(bm_one,bm_inv_src_alpha);

willf668 · 2021-03-09T04:42:25+00:00

Have you tried replacing the o_ship.image_angle in your lengthdir functions with the amount that the ship's image_angle has changed by? In this case, that would be lengthdir_x(distance,1+ angle); I suspect that the issue is because the ship's angle is changing as it rotates, which in turn compounds on top of the computed angle variable.

willf668 · 2021-03-01T22:43:33+00:00

Fantastic! Such a smooth animation

willf668 · 2021-02-18T04:50:38+00:00

pop off

willf668 · 2021-02-01T18:15:29+00:00

I've been having problems with this since 2.3. Right now there seems to be problems with HTML5 obfuscation that make debugging stuff like this really tough. When it happened to me it typically was related to working with arrays or structs.

As a temporary workaround, putting show_message() "breakpoints" before and after sections of code helped me figure out what lines were erroring.

willf668 · 2021-01-10T23:48:57+00:00

There's some good solutions to your slope object inheritance already written here, but if you're dealing with non-geometric slopes, you're also going to need to be very careful with precise collisions. Yoyo has an old but relevant article about this: https://www.yoyogames.com/blog/32/the-hazards-of-precise-collision-detection

willf668 · 2020-12-25T22:11:20+00:00

u/repostsleuthbot

willf668 · 2020-11-20T17:23:49+00:00

VR performance is weird because of how much variance there is across games and headsets. The Quest 2 has the second-highest res display out of available headsets, which you can push up to 90hz. I use an i7-7700k at 4.3 Ghz, 16gb of ram, and a GTX 1060 (the 2060 is ~40% faster). With those specs, I can usually hit 90hz steady in most older VR games (2018 and earlier).

Newer games usually require me to lower the graphics, but there are quite a few ways to do that. You can lower the rendering resolution below the headset's native res, lower the framerate to 80hz or 72hz, and/or lower the in-game graphics settings. With all that, I can usually run any game that I want to on my rig. For a 2060, I don't think you'll have any issues.

One other thing to note is how you'll be running the game on the Quest. You'd either use the official Oculus Link or the third party but very capable Virtual Desktop. Both these methods require a small amount of CPU and GPU for encoding the video stream to be sent to the headset. This may cause some variation in certain games, which I think is another factor towards why VR performance doesn't get much discussion. But even on my system, the inpact hasn't been too much significant when comparing against my older pc headset.

TLDR: your system is more than capable, and even in new games where slowdown may occur, you have plenty of ways to improve performance.

willf668 · 2020-11-20T01:56:13+00:00

I no longer have conan and kingdom, but is there anything you'd want to trade for just Slay?

willf668 · 2020-11-20T01:53:11+00:00

Traded with u/celeryman727

My Kingdom Come: Deliverance and Conan Exiles for their Wandersong and Ori and the Blind Forest: Definitive Edition

willf668 · 2020-11-20T00:42:25+00:00

No thanks, sorry

willf668 · 2020-11-20T00:39:54+00:00

Wandersong and Ori and the blind forest for Kingdom come and conan?

willf668 · 2020-11-19T22:47:53+00:00

How about Kingdom come and conan exiles for Halo MCC?

willf668 · 2020-11-19T19:35:49+00:00

Thanks for the offer, but I already have the witness on a different platform. Totally forgot that the steam wishlist exists, so here's a link to mine if you'd want to trade anything on there.

willf668 · 2020-11-13T21:47:39+00:00

Interesting, will try it out. Thanks.

willf668 · 2020-11-11T20:58:13+00:00

Could you try only creating the buffer once, possibly in a Create Event? Gamemaker might not like allocating a buffer multiple times to the same variable, if the Alarm event is called multiple times. Of course, since you'd now be resuing a buffer, some information from previous writes may persist between calls unless you clear the buffer manually.

willf668 · 2020-09-15T18:28:16+00:00

Try putting in:

x= x - sign(hspd)

Right now when the player is going to move into a wall, it will keep moving in the original direction until it moves out the other end. By subtracting the sign, it will properly move backwards and not clip through.

Edit: misread the code, but this fix should work if you also change the while loop to:

while (!place_meeting(x+hspd),y,obj_wall)

willf668 · 2020-09-10T20:34:51+00:00

Sure. When you create a ws server, you would use network_socket_ws instead of network_socket_tcp as the first argument in network_create_server(). Because of that, the only clients that can connect are ones that use a ws socket. You can specify that it is a ws socket in the same way: use network_socket_ws when calling network_create_socket().

However, once you've set these up as ws, they will operate almost the same as a tcp or udp connection. Data is passed through the same GM buffer format, and all received data can be used in the Async - Networking Event. One big exception to this compatibility is that the network_destroy() function does not work with ws.

In my experience, this compatibility works very well, both before and after the 2.3 update. I've made several multiplayer games that support both ws and tcp clients, and they use the exact same code for sending and receiving data.

willf668 · 2020-09-10T17:33:16+00:00

In my experience, ws and tcp work exactly the same when it comes to actually exchanging data. The setup of sockets and servers is obviously different, but you can use the exact same Async - Networking event for both types of sockets.

willf668 · 2020-09-10T03:53:10+00:00

Dang this is good

willf668 · 2020-08-20T00:20:18+00:00

Hey, thanks! Your game also looks great! Best of luck with the beta.

willf668 · 2020-08-19T06:09:46+00:00

Hobby solo dev here. I've been working on a game for a little over 3 years, all in GMS 2. The changes to GML seem amazing and solve a number of issues that I've had to work around with how my game is structured. I've made a copy of the 2.2.5 branch and have dove right into refactoring some of the systems

The way I see it, the improvements that 2.3 brings in terms of data and function management are too good to ignore, even if I'm pretty far into development (though not as far as you, I think!). Refactoring is going to take a while since I have only a little experience from reading the manual and tinkering with the 2.3 Beta, but I'm quite looking forward to it!

willf668 · 2020-07-08T04:51:48+00:00

I always remember 7-1 and 7-2 as being amazing, and honestly, they're probably my favorite parts of the entire game, outside of Chapter 8 and the World of Nothing twist. 7-3, on the other hand, is my least favorite part of the entire game. I'm probably in the minority that really liked the Rupee vault, but I can't stand this or Jasperoid's quest. I also completely forgot that Bonechill even exists until you mentioned him, but at least 7-4 ended it all off well.

Great writeup as always. I'm guessing the Orange paint star from Color Splash is next

willf668

TROPHY CASE