projectile | friendly tool for throwing stuff around inside Blender | Addon library

Hello i make my 2d game with unity and i feel confuse about oop design. There is a 4 class in my game.

1. StageView : The view(scene) where the game logic run.

2. ObjectPool : The object pool that can manage the gameobjects, and it is the member field of stage view. (It is not a singleton)

3. Projectile : The projectile class that can attack the monster.

4. Monster : The monster class that could be attacked by projectile.

I am using numericImput to get the data introduced by the user.

I am trying to graph the balistic curve of the proyectil motion described by the input of the user (The user gives a value for intial velocity, angle measure, time of flight and k constant), but I can't solve the mistake :(

Any help would be thanked! :D

Here is my code

I'm trying to make a basic FPS game in Unity and I'm having an issue where the projectiles I shoot won't instantiate in the right place. From what I can tell, the projectile instantiates in roughly the same position relative to the player regardless of where I look (that position being a little to the left of the starting angle of the player).

Here's a 20 second video demonstration of what I'm talking about.

https://youtu.be/WLVuqUtMqd0

Even when I'm facing the exact opposite direction of where the projectile usually instantiates it still spawns in the same place, which means the projectile ends up spawning behind the player and hitting the player.

I tried using Debug.DrawRay() to see if maybe the firepoint itself is wrong (which would be shown by the ray starting somewhere other than the gun barrel). However it seems like the starting point of the ray is correct every time.

I'm not sure if this is related to the issue above, but I have noticed that the ray direction is wrong if I'm looking a little below the horizon. It seems like the projectile's direction is correct regardless though.

Ray directions when looking slightly above the horizon vs. lower

Here's my code for intantiating/shooting the projectile. I think the most relevant parts are probably shootProjectile() and instantiateProjectile(). This script is attached to the player character.

System: Linux Mint 20 Emacs version 26.3

I updated all packages with package-list-packages and then ran M-x prelude-update. After restarting emacs with emacs --debug -init I get this error:

My screen is 1920 x 1080 and the display that I have drawn everything on is 960 x 540. I have a projectile which does an equation with the position of the mouse to determine its trajectory but because I have up scaled everything the mouse pos is still acting like its 1920 x 1080 and not 960 x 540.

Class method for projectiles trajectory ( I have camera movement which is why player.rect.x is being subtracted by scroll )

I know this question has been asked before but I'v tried different approaches and I can't seem to be able to fix it.

I know I have to reset my important global variables in order to correctly restart the game. The reset of those variables is done when lives == 0 -> I reset the global variables, main menu becomes True and Game False which should put me back in the main menu.

However when I run my game, as soon as the lives reach 0 the code finishes and exits -> Process finished with exit code 0.

The issue must be in my while game loop but I'm unsure what I'm doing wrong. I'v also tried wrapping my game logic in a function, this seems to mess with my game since I only get the frozen state screen, no enemy spawning and not able to move.

Any ideas what might cause this issue?

Full code:

I'm new to Pygame and trying to learn about sprites and collision detection. I found some code and tried to add some functionality to it.

The basic idea is that I have a polygon which can be rotated in place. When the user presses SPACEBAR, the polygon fires a projectile which can bounce around the frame. If the projectile hits the polygon again, I would like to quite the program

First of all, here is the code

Using this link as a guide, https://www.geeksforgeeks.org/difference-float-double-c-cpp/#:~:text=double%20is%20a%2064%20bit,15%20decimal%20digits%20of%20precision. double is a 64 bit IEEE 754 double precision Floating Point Number (1 bit for the sign, 11 bits for the exponent, and 52 bits for the value), i.e. double has 15 decimal digits of precision , the below code does not maintain 15 decimal digits of precision. Rather, 14.

It is for simple projectile motion calculator, where, the range of a projectile launched at 30 degrees should match that of the same projectile launched at 60 degrees.

I am programming a game for years now but I have a question about how I programmed things up.

So imagine you have a gun class for a game, guns can have many sprites, sounds, casings, projectiles, parameters, etc. So then I just need to create another class extending this gun class and fill my abstract methods up with what I need that particular gun to do.

So I made an abstract class to handle all of the internal code of the gun, if it shoots, if it needs bolt action and how long it has to wait, when to play the fire sound, etc. So basically the main gun class calls for the actual gun class (that is filled with abstract methods) for these parameters.

So my question is, if I am calling these abstract methods over and over again as needed throughout the code is it bad to have the following?