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.
Messages - ben_g
Pages: 1 ... 29 30 [31] 32 33 ... 71
451
« on: November 09, 2012, 04:09:42 pm »
What this community needs is a really great game or tool. Maybe if for every popular platform a group of good programmers would work together to create a really awesome program, we can get more new people interested in programming them. So basically we have to show the world how powerful calcs really are.
But this is just a suggestion. I don't know at all how good/bad it will work
452
« on: November 08, 2012, 02:56:06 pm »
I wonder if they have also increased the memory size. Well, they kinda have too, since a 320*240 graphic buffer is, assuming a very common 16bpp, 153600 bytes. This is way more than will fit in RAM. In fact, it's so much larger that this calc will probably have more RAM memory than the old 84+ has flash.
453
« on: November 03, 2012, 04:56:10 pm »
If you only need to move one pixel around, you should use pxl-off instaed of cleardraw. It's a lot faster, especially when you have got a level as well since then you don't need to redraw the level every frame.
454
« on: November 02, 2012, 02:46:59 pm »
an other bug report: when underwater, pressing D will make you able to go trough walls. I also noticed that sand when it falls sometimes leaves behind a dirt block at it's original location. (This is in the most recent version)
455
« on: November 01, 2012, 05:40:28 pm »
That does indeed look like raycasting. The extremely wide aspect ratio is one of the causes why it looks so bad. An other one is the scale of the bars. The corners look more like gentle curves. You should make walls that are further away smaller and the ones closer bigger.
456
« on: November 01, 2012, 05:20:34 pm »
BUG REPORT: The jumping looked all right at the start of the game, but as soon as I started destroying blocks, the framerate dropped to approximately 1fps, and from then it started going slower and slower untill I had to hold down escape for over 10 seconds to close it.
457
« on: November 01, 2012, 05:14:38 pm »
growing beards and mustaches for prostate cancer? I've never heard of that action before...
458
« on: October 31, 2012, 07:00:12 pm »
Welcome to the forums! Have some peanuts:  To answer your question: If you're still new to programming, I'd reccomend to start with basic, and after a while you can move to axe. Basic works exactely the same as the homescreen, but with some extra programming functions (like if, for, while, ...), so when you can use the calculator, you can use basic. Axe is a lot more low-level, which means that you will have to place some elements in the correct part of the memory yourself. Because of this, there is a lot more that can go wrong. Also, basic has an emergency stop, the ON key, but when your axe program stops responding, you have to take out a battery, resulting in a RAM clear. These things aren't really bad for your calc, but they can get annoying when they happen a lot. That's why I reccomend starting with basic. And when you're good with basic, give axe a try. It's a great language.
459
« on: October 30, 2012, 06:55:21 pm »
This sounds like an interesting project, but unfortunately all of the previous similar projects have died.
Do you already know how it might look like and what hardware it will have? If you want low power consumption and still want to make it powerfull, you should consider using 2 CPU's: a cheap, slow one that uses almost no power (z80?) to do some basic stuff, and a more powerfull one that can be turned on or of trough software too use for gaming or as a speed boost for advanced math.
For the LCD, the most battery-efficient ones are simple B&W screens, but color LCD screens with no backlight or a backlight that can be turned off gets good efficiency as well. Just make sure it has a good reflector so you can still see when the backlight is tured on. And don't use a touch screen when it isn't nessicary. Calculators can be smashed around quite a lot when they are in a back pack, and touch screens are often made of very tin glass that breaks easly. For the rest, you can add some other nice hardware such as USB ports, wifi, ..., and if you make sure you can turn them on and off trough software, it shouldn't consume the battery too much.
460
« on: October 28, 2012, 06:29:18 pm »
Outside of school, your calc should be relatively safe. Thieves are usually only interested in more common devices such as cell phones and MP3 players.
In school it's a different story, but you can often avoid people stealing your calc by putting a cheap calc in your backpack, in a place you'll see before you see your expensive graphing calc. People often assume everyone has only got 1 calc unless they know you.
461
« on: October 28, 2012, 06:20:51 pm »
Hi and welcome. Have some peanuts potatoes:  What calcs do you have? only an nspire?
462
« on: October 28, 2012, 05:53:15 pm »
This looks like a nice game.
It's quite unrelated, but I wonder if those games could be converted or the source code recompiled to work on the 84+. The screen looks very similar and it looks like processing speed is not much different from that of the calc.
463
« on: October 26, 2012, 01:50:29 pm »
It looks good so far, but I would recommend to lower the field of view, so you get less perspective distortion, which makes it look a bit more realistic.
Also, a single 3D point is called a vertex, and multiple points are called vertices.
464
« on: October 18, 2012, 01:54:00 pm »
My school doesn't have calculators. All calculators used during class are owned by the students, not by the school.
465
« on: October 16, 2012, 02:55:22 pm »
You should make an account on GitHub and make a "fork" of KnightOS. It took me a while to figure it out since i've never used git/github before, so here's what i did:
1. You need "git" installed.
2. Make an account on github.com, and click "fork" on the KnightOS github page.
3. Choose a directory for the project to go into (it will create a directory called KnightOS there)
4. From the terminal/command prompt: "git clone [address of your cloned project]". For me, this was "git clone https://github.com/chickendude/KnightOS/"
5. Go into the lang folder and create a folder with your language name (nl_be, de, es, etc.) and copy your translated files. Make sure they are encoded in ANSI (Windows-1252) (not UTF-8 or some other format). I think files written in Notepad are ANSI by default.
6. From the terminal "git commit"
7. Again, from the terminal "git push". You will need to type in your username followed by your password, and it will upload your changes to your fork.
8. Now all you have to do is log on to github, go to your KnightOS fork, and make a pull request (there's a button above the project that says "Make a pull request") and you're done.
It took me a while to figure it out, but once you get everything figured out altogether it takes less than a minute from the initial download of the project to the final push. In the future, when updating your files, just go into your KnightOS git project directory and run "get pull" to make sure there haven't been any changes since you last updated. There are also some GUIs, but i couldn't figure out how to get any of them to "push" the changes to the internet 
Again, make sure that the files are ANSI formatted!
I'd be more than happy to help anyone who's having trouble 
I got to the git commit, then suddenly this window appears and I don't know how to save or confirm or do whatever I'm supposed to do
Pages: 1 ... 29 30 [31] 32 33 ... 71
|
Show Posts