Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
what is your reasoning behind inverting the rotation?I noticed that when the target was above, it was vertical, but when you went to the top-right, it leaned left. Also, when you weren't perfectly above (you were slightly to the right), it leaned slightly to the left.
Glad it worked and that I could be of some help
Rotation-wise the laser needs to be flipped so you could try inverting the rotation i.e. return -rotationAmount;
For a better understanding of how the laser reacts to different positions, try clicking on points all the way around the emitter ("tank") - not just horizontal and diagonals - and also different distances from it.
If you want the bottom, don't divide height by 2; that would give the centre.
Thanks for the in-depth response.You are welcome.That function is being put into an update() function which is constantly updated while the window is open, so that shouldn't be an issue. It will only be destroyed when the window is closed.I think you misunderstand.
What I mean isvoid func() {Variables declared on the stack only live until they go out of scope (in this case the scope being the function). It doesn't matter if you call the function from somewhere else continuously.
int a = 42;
// pass a pointer or reference to "a" to someone else
} // At this point "a" is destroyed, so that pointer or reference you passed to some other function is now invalid.
For example:void f(int a) {In the above program, the variables "b" and "c" are going to be created and destroyed 10 times each - once every time the function is called. It doesn't matter that "f()" is called inside the loop until the program exits - the variables inside the function are not kept alive from one invocation to the next.
int b = 5;
int c = a * b;
std::cout << "c is " << c << std::endl;
}
int main() {
for (int i = 0; i < 10; ++i) {
f(i);
}
}
This is fairly basic C++ knowledge btw.
Ohh and one other thing; concerning what Nexus said:
You want to make sure that you are not building your application in debug mode but linking to the release mode libraries or building in release mode but linking to the debug libraries. That's what's meant by "mixing debug and release".Thanks for the link and increasing my warning levels, will try them and report back.Looking forward to hear what you find :-)
well, your "defaultFont" is a stack (automatic) variable in the game::gui() function, so as soon as that function exits it is going to be destroyed and any reference to it past that point is going to go bad. Could that be your problem?
If not, then perhaps try running your code under a tool like Valgrind (http://www.valgrind.org/) or do a build with gcc (4.8+) or clang (3.4+) with -fsanitize=address enabled (read more here: http://clang.llvm.org/docs/AddressSanitizer.html) and see what that finds. Both those tools are rather excellent in tracking down memory corruption bugs.
Ohh and before you do that, bump you compilers warning level to the max and check/fix all the warnings - most compilers are pretty good at spotting silly mistakes as long as you let them (by upping their warning level).