Delay for the shot


#9

Actually, you could just apply ‘gravity’ to the bullet every frame that it is going forward (world down * magic number * deltaTime). That would do enough to look like a bullet falling over a distance.


#10

If I be used gravity from the physics engine, and adjust the mass parameter, will it work?


#11

If the bullet has a rigid body and collision, then yes but I don’t recommend that bullets should use the physics engine due to their size and speed.

For large things like geneades, perhaps.


#12

Thanks for the detailed explanation. Now in my project, shooting works well, but sometimes the bullet flies through the object. How can this problem be solved?


#13

Assuming it isn’t using a rigidbody with collision:

Have the bullet keep track of it’s position in the world and do a raycast between it’s current and last frame position.


#14

I tried this method, but it did not work. Could you help me? :slightly_smiling_face:


#15

Try this version: https://playcanvas.com/project/596138/overview

A coupe of issues that I fixed:

  • The last position was updated after the entity had moved which meant that both the last position and the current position was the same.
  • The position of the entity wasn’t copied to last position, it was just storing a reference to the position vector.

#16

Great job. Now I understand my mistakes and how to do it right. :grinning:
Better not to use setTimeout(), but to use the deltaTime variable for all counters?


#17

In your case, it looked like you were setting a setTimeout every frame the bullet was ‘hitting’ anything and because the code destroys the entity on ‘hit’, you can be left with dangling setTimeout calls which leads to exception errors.

The way I’ve done it means that there’s only one place that the entity is destroyed for the bullet.


#18

Is my project correctly implemented the algorithm for calculating the target point for the bullet or can it be simplified?


#19

From playing it, it looks a bit off. It’s almost as though it doing a raycast from the camera and not the players weapon. I haven’t looked at the code to be sure.


#20

I simplified the script for the bullet, and I have new questions. :grinning:

  1. Can I somehow make a check on another entity, that Ray Cast from this script was successfully applied to it, and after that play, for example, a sound?

  2. If I have a trigger in my scene, but it doesn’t have a Rigid Body component, can I do the same check, that Ray Cast was applied, but ignore this so, that the .applyImpulse() method doesn’t throw an error?

  3. When I start the game, the bullet entity is disabled. When I take a shot, it’s copied. Euler angles always have the same value, regardless of where the weapon is directed. I have to set the Euler angles for each new bullet entity based on the Euler angles of the point that is at the end of the weapon. Can this be avoided?

I want to make the all scripts standalone so that they fit the design pattern ECS. :slightly_smiling_face:


#21
  1. Not sure what you mean by this? If you are talking about telling the entity that it has been hit so it can do something in response, you can fire an event on the hit entity that scripts on that entity is listening for.

  2. Check if the hit entity has a rigidbody before applying impulse. (if (hitEntity.rigidbody != null) or something similar.

  3. Not really. You could put the bullet as a child of the weapon and place it at end of the barrel. When you clone, it should place it in the correct position to start from? This may cause problems if you reparent the bullet though. I would just stick to cloning it and positioning the clone in the correct place.


#22
  1. That is, I can configure the connection between the two scripts by this instruction?
  2. Here I understand.
  3. That is, I should always set Euler angles for the bullet entity, that I should be getting from another entity?

Sorry for a lot of questions. :sweat_smile:

Edit: I figured out with point 3. :grinning:


#23
  1. Yes. Entities have and components all can fire and listen to events which is incredibly useful

#24

You wouldn’t happen to know, there is rules for writing scripts based on architectural pattern Entity Component System?


#25

PlayCanvas script systems is more of a EC rather than ECS.

Quite frankly, I use the SOLID principles where possible.

I made this a while back (not sure if it still works with latest engine changes) which encompasses my approach in keeping code modular.

https://playcanvas.com/project/560025/overview/isometric-base-builder


#26

I, as a beginner, it is very interesting. :slightly_smiling_face:

I still have one more shooting question. How to set correctly the crosshair on the screen? I use the .worldToScreen method to set the crosshair, but it is installed incorrectly. I have to adjust it by pixels, which is not correct.


#27

As the crosshairs are on a 2D UI screen, you actually want world to UI space rather than world to screen (screen being your computer screen and working in pixels).

Unfortunately, there isn’t a built in function in PlayCanvas to do that but a few forum users have managed to work out how to do this: [SOLVED] Include devicePixelRatio for screenspace to worldspace conversion


#28

Thanks. I found this formula and applied it in my project. The crosshair should be at the bottom left of the screen.

var screenPos = new pc.Vec3();
var screenEntity = this.entity.element.screen;
var scale = screenEntity.screen.scale;
var device = this.app.graphicsDevice;

this.cameraCrosshairEntity.camera.worldToScreen(worldPoint, screenPos);
this.entity.setLocalPosition((screenPos.x / scale) - (this.entity.element.width / 2), ((device.height - screenPos.y) / scale) - (this.entity.element.height / 2), 0);