[QUOTE=ZenX2;39802819]That's the entity that threw it. The problem is that it says true for being equal and inequal[/QUOTE]
Simple calculus:
[i]self.th[b]r[/b]ower =/= self.th[b]ow[/b]er[/i]
How did I not notice that
That's what we thought too :v:
I killed this guy by throwing my pistol at him twice. This means gameplay is now possible
[img]http://puu.sh/2clvM[/img]
[editline]4th March 2013[/editline]
[QUOTE=Map in a box;39802968]That's what we thought too :v:[/QUOTE]
Honestly I saw it all as self.thrower
[QUOTE=Deco Da Man;39794452]Unless you're developing for a very obscure platform, just use the provided make files.
No external headers or libraries are required, it compiles out of the box and it compatible with the Lua 5.1 API and ABI.
[b]Edit:[/b]
Argh, worst page-king D:
Uh, I'm working on reading this, for uni!
[IMG_thumb]http://i.imgur.com/Ao5rK79.jpg[/IMG_thumb][/QUOTE]
hey man at least we get fuckin dinosaurs on the operating system book
[T]http://i.imgur.com/Waru2TZ.png[/T]
how cool is that
Shadow mapping is working now! Currently using 3-split cascaded variance shadow mapping for the sun, might upgrade to 4-split - depends if I can be bothered to write gaussian blur shaders to blur the shadow maps or not. Got rudimentary models loading too (no materials yet).
[img]http://i.imgur.com/m4L9FWF.jpg[/img]
Also did a bunch of optimizations thanks to Visual Studio 2012's profiler (which is awesome btw).
[editline]5th March 2013[/editline]
dat jpg rape
[QUOTE=Em See;39803130]hey man at least we get fuckin dinosaurs on the operating system book
-image-
how cool is that[/QUOTE]
Dude.
Gimmie. :v:
[QUOTE=Larikang;39801574]It takes some practice to get used to using git branches effectively, but it's definitely worth it. Terrible merges are almost always due to terrible use of branches, and aren't a necessary part of using git.[/QUOTE]
I mean pushing and pulling branches. It seems this is better now, but last time I checked TortoiseGit didn't reflect the change and still selected only one branch in the push GUI.
Started toying around with PyCOLLADA. The screenshot below shows just how easy it is to grab data from COLLADA files using PyCOLLADA.
[img]https://dl.dropbox.com/u/16024664/pycollada.png[/img]
I've decided I'm going to use COLLADA as my intermediate model format. With PyCOLLADA it should be really easy to convert COLLADA files to my model format.
Prettier place holder graphics, woo. Recording the screen on Windows 8 is quite laggy compared to Linux on this computer :v:
[video=youtube;Ihu5MIksJXU]http://www.youtube.com/watch?v=Ihu5MIksJXU[/video]
[QUOTE=Dr. Evilcop;39804323]Prettier place holder graphics, woo. Recording the screen on Windows 8 is quite laggy compared to Linux on this computer :v:
[video=youtube;Ihu5MIksJXU]http://www.youtube.com/watch?v=Ihu5MIksJXU[/video][/QUOTE]
Your camera deadzone is far, far too big.
I wonder if there exists an esoteric programming language designed such that programs in it can easily be transmitted from one person to another by spoken word.
I'm fairly pleased with my project [url=https://github.com/inkadnb/rupture]directory structure[/url] so far.
RuptureBuilder will be in charge of converting various media files to a format the engine can interpret, among other things.
RuptureCOLLADA is in charge of converting COLLADA files to the engine's model format.
I'll probably combine RuptureBuilder and RuptureCOLLADA eventually. I've got them separated right now because I haven't bothered trying to link python and calling it from the Builder that way. Plus, having the Python COLLADA builder as a separate project makes it so much easier to debug since I can use the Python debugger within Visual Studio using [url=http://pytools.codeplex.com/]PyTools[/url].
I wrote a short method in my DLL to read and dump a converted model's vertices which is called by the Builder application. Works good so I think that's a good stopping point for today.
I'll probably start designing the actual model format tomorrow.
[QUOTE=Map in a box;39799160]You think you've had it hard?
[IMG]http://puu.sh/1n1Y0[/IMG]
Source control hell.[/QUOTE]
You think that is bad?
[IMG]http://i.imgur.com/oixvTg2.png[/IMG]
Who are you people letting near your repositories.
[QUOTE=CountNoobula;39804984]You think that is bad?
[IMG]http://i.imgur.com/oixvTg2.png[/IMG][/QUOTE]
[img]http://i.imgur.com/H54qa9B.png[/img]
github provides a nice graph like this...
[img]http://i.imgur.com/ccNtj3H.png[/img]
But if you [URL="https://github.com/octocat/Spoon-Knife/network"]try to do it[/URL] to the spoon repo...
[t]http://i.imgur.com/Lu8bHmK.png[/t]
[QUOTE=Em See;39803130]hey man at least we get fuckin dinosaurs on the operating system book
[T]http://i.imgur.com/Waru2TZ.png[/T]
how cool is that[/QUOTE]
To be fair, no book can quite compete with the awesome nerdiness inherent in the Dragon book.
[IMG]http://www-fp.pearsonhighered.com/assets/hip/images/bigcovers/0321486811.jpg[/IMG]
In any of its iterations:
[IMG]http://gazonk.org/~eloj/images/cover_dragon.png[/IMG]
Playing around with fractals
[vid]https://dl.dropbox.com/u/17738517/Videos/mandle01.webm[/vid]
It's a tad laggy for my linking, but that's what I get for doing it all on the cpu and not using openGL.
[QUOTE=Darwin226;39795838]Yeah. It's much better to use command line all the time and not know how to do anything at all.[/QUOTE]
Whether you use the command line or the GUI, your brain still needs to figure out what it's doing. You learn the GUI the exact same way you learn the command line, by reading documentation and experimenting.
[QUOTE=esalaka;39801795]In fact, git was designed to handle merges as well as possible. Terrible merges should only result from mofidying the same lines in several branches - and even then, the three-way merge should be relatively trivial, if git even finds it necessary.[/QUOTE]
In fact you should be merging much less on git than svn/hg. Rebasing against upstream makes it trivial to have clean merges.
[QUOTE=Tamschi;39803806]but last time I checked TortoiseGit didn't reflect the change and still selected only one branch in the push GUI.[/QUOTE]
Use 'git pull <remote> <branch>' and 'git push <remote> <branch>'.
[QUOTE=HiredK;39794584]Have you implemented networking yet? If so how do you handle client-side prediction?[/QUOTE]
Sorry, forgot to reply to this. Yes there's networking. I predict weapon firing and player movement. There's no correction going on though, the movement code is only running client-side for now. It does mean you can cheat very easily because your position is just sent to the server but I'm not worrying too much about that at this stage.
Quite aware of most lag compensation, prediction and interpolation techniques before someone posts that Valve article lol.
[QUOTE=Da'Jobat;39805907]To be fair, no book can quite compete with the awesome nerdiness inherent in the Dragon book.
[IMG]http://www-fp.pearsonhighered.com/assets/hip/images/bigcovers/0321486811.jpg[/IMG]
In any of its iterations:
[IMG]http://gazonk.org/~eloj/images/cover_dragon.png[/IMG][/QUOTE]
oh I don't know man, it definitely wins the nerdiness awards but at least the concept makes sense, as labelled in the first
... but what the fuck do dinosaurs have to do with operating system theory
[IMG]http://i.imgur.com/XLl6WVv.jpg[/IMG]
oh crap, as for what I'm working on other than reading the above book uh
well I've been throwing my first packets against my laptop and managed to make them stick
and like
move a ship like in asteroids
but with the mouse aiming it
and other players can join in and they can join in on the non-existent fun
[t]http://i.imgur.com/5thFZj0.jpg[/t]
in all seriousness when I finally got it to work I was so happy
and I played around with a mate over the intertubes
the main issue is it trusts the client; the client calculates and sends position, velocity and direction to the server, which iterates using that and passes all players back all the other player's current states
each client then uses the other player's velocities to simulate forward until next update, so it kind of smooths it out, but not really since interpolation would mean smoothing the changes in updates, no?
next up is a side scrolling networked dog simulator where text input is evaluated for a rough syllable count which is then used to generate woofs and so on.
don't ask
[QUOTE=Nikita;39804899]I wonder if there exists an esoteric programming language designed such that programs in it can easily be transmitted from one person to another by spoken word.[/QUOTE]
[url=http://shakespearelang.sourceforge.net/report/shakespeare/shakespeare.html]This one can be performed by humans.[/url]
[QUOTE=gparent;39807348]Use 'git pull <remote> <branch>' and 'git push <remote> <branch>'.[/QUOTE]
This is what the GUI does, what I couldn't find was a function to push/pull all/all matching branches.
I prefer having a good GUI to CUI, but I think I should just give up in regards to Git and just use the console when Hg-Git doesn't push properly.
[QUOTE=gparent;39807348]Whether you use the command line or the GUI, your brain still needs to figure out what it's doing. You learn the GUI the exact same way you learn the command line, by reading documentation and experimenting.[/QUOTE]
That's not completely true. GUI can explain what you need to do and what you can do better than the command line can.
Like walking in an FPS or walking in a text adventure. Conceptually the same but the first one is more intuitive. At least to me since I have very little experience in doing stuff through the command line.
[QUOTE=Darwin226;39807773]That's not completely true. GUI can explain what you need to do and what you can do better than the command line can.
Like walking in an FPS or walking in a text adventure. Conceptually the same but the first one is more intuitive. At least to me since I have very little experience in doing stuff through the command line.[/QUOTE]
irrelevant, you still need to know the concepts of git.
[QUOTE=Map in a box;39799160]You think you've had it hard?
[IMG]http://puu.sh/1n1Y0[/IMG]
Source control hell.[/QUOTE]
That's really not [I]that[/I] bad, you could rebase two branches and be completely synced.
[QUOTE=danharibo;39808502]irrelevant, you still need to know the concepts of git.[/QUOTE]
This discussion has gone in a completely irrelevant direction to my original situation. I'm not blaming git, github, git command line or github for windows for what happened. I realize that this is what I get for using it half assed.
What my orignal statement about using UI versus command line meant is that, for what I use git, UI was a much, much simpler option.
[editline]5th March 2013[/editline]
[csharp]
hello = function [String name]
{
printLine ("Hello " + name);
};
hello "Luka";
hello "FP";
hello "World!";[/csharp]
This works now.
[QUOTE=laylay;39807410]Sorry, forgot to reply to this. Yes there's networking. I predict weapon firing and player movement. There's no correction going on though, the movement code is only running client-side for now. It does mean you can cheat very easily because your position is just sent to the server but I'm not worrying too much about that at this stage.
Quite aware of most lag compensation, prediction and interpolation techniques before someone posts that Valve article lol.[/QUOTE]
You mean this one? [url]https://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking[/url]
[editline]5th March 2013[/editline]
[sub][sub][sub]don't hurt me.[/sub][/sub][/sub]
[QUOTE=Darwin226;39807773]That's not completely true. GUI can explain what you need to do and what you can do better than the command line can.[/QUOTE]
Tamschi is literally living proof that GUIs make your life needlessly harder. He wouldn't have needed to post here if he were using CLI because "--all" is the first option that appears when you type "git push --help".
One thing I've noticed is that the people who say git is complicated are usually GUI users. Once you learn what you're doing instead of taking wild guesses at a GUI frontend, that's when the simplicity of git really shines. At that point you realize that the GUI abstractions were hurting you, not helping.
EDIT: If you want to use a GUI, go for it, but the real reason is that people are too lazy to type and learn what they're doing. When you take efficiency into account, GUI dies a rapid death.
[QUOTE=gparent;39809719]Tamschi is literally living proof that GUIs make your life needlessly harder. He wouldn't have needed to post here if he were using CLI because "--all" is the first option that appears when you type "git push --help".
One thing I've noticed is that the people who say git is complicated are usually GUI users. Once you learn what you're doing instead of taking wild guesses at a GUI frontend, that's when the simplicity of git really shines. At that point you realize that the GUI abstractions were hurting you, not helping.
EDIT: If you want to use a GUI, go for it, but the real reason is that people are too lazy to type and learn what they're doing. When you take efficiency into account, GUI dies a rapid death.[/QUOTE]
I think git is easy and I prefer the Windows GUI version. Even though I use the command line version more because I work primarily on a Linux dev machine.
It takes seconds to make a commit and push it to GitHub.
Sorry, you need to Log In to post a reply to this thread.
