Awesoooooooome! This is really cool! I love Star Fox, I played it on an emu, stopped at either a level where you have to align your plane to a given formation or a level where the boss refused to die after hundreds of retry ... . Great work Jasoco! [Need to enlarge the window, barely can see the las...

Here are some remarks, sorry for not being helpful with the crash. ===Bug?=== game closed at pushing barrel (instead of stabbing it) stepping inn's door stepping shed's door (shed key obtained) pressing 'e' outside the forest turn on debug text (pressing 'd') when there's a dropable on screen On the...

Happens for me too. Will look into that. Hey, it's rude! It's been a while, how are you? Please take a look and send me some feedback. :ultrahappy: At least part of the problem, or so it seems to me, is the usage of characters in the conf.lua title setting that aren't UTF-8 - they look to be using ...

I had rewritten the code to check whether there was something I missed. But everything seemed fine (to me) and the program crashed still. :? Curious, I rewritten the program again without any features other than reading the "particleProperty.txt", loading it to a table and then setting it ...

On my Ubuntu the draw.love program looks just fine (no artifacts). . Maybe some driver setting? (far-fetched, I know) You're right, bartbes! I skipped the 3d settings because I simply thought that LÖVE is a 2d game framework... . I'm sorry, It's not a bug in LÖVE but is caused by the graphic driver...

Oh, and I use a look-up table to handle the shifted characters. That's not necessary anymore -- we have the unicode argument now, which works for every key and (IIRC) for different keyboard layouts as well. Ow, sorry, I am still working in 0.6.0 and haven't read the new features. Waa, I really have...

--===Spec===--

• WinVista
• Intel Core2Duo T7300 @ 2.00GHz
• Mobile Intel(R) 965 Express Chipset Family 358MB
• 3062MB RAM

--===Result===--
2 - 3 FPS
--===Average Execution Time===--
1.32 second per function call (deviation +/- 4.2%)
[40 sample @ timeLab1.5]

wow, that'd be a creepy shader!

I check the length of the key like you have mentioned. I think that's quite nice enough. Oh, and I use a look-up table to handle the shifted characters. You could see my code in the programme posted here: [RLC]Data Execution Prevention?.

I hope that's helpful.

Waa, thanks for the insight, Kikito. :ultrahappy: These latter optimizations are usually paradigm shifts - your code is rearranged so it does the same thing, just in a completely new way. For example, using a QuadTree or the A* algorithm instead of brute force. Ah, I mean, if the QuadTree (the optim...

Very mysterious... the only thing I can think of here is that you might be doing more between timing than you realize. The main program basically just double loops that collect times. After they have finished turning round and round, the program writes the data to a file. That's all. I have deleted...