Jump to content

  • Log In with Google      Sign In   
  • Create Account

irbaboon

Member Since 07 Oct 2011
Offline Last Active Today, 02:03 PM

Posts I've Made

In Topic: input in realtime.

Today, 08:09 AM

 

Every time I see a "realtime" thread, one moronic wannabe just shows up trying to make the OP feel as stupid as possible.
It is incredibly obvious that the OP is a beginner, and doesn't need actual realtime input.


Correcting misconceptions of a beginner is a very important step, especially because such misconceptions can make researching your own answer extremely difficult because the keywords you use are not the keywords which will be helpful. I did not see what tonemgub wrote as something to make someone feel stupid.

 

 

I just feel there are other ways to explain the difference.

 

I won't deny the fact that I'm overreacting, but it's just that I think beginners do not need to know things like this at the stage they're in.

They will probably not understand what you are talking about with the knowledge they have, so they will assume it's hard to check for input or use a timer.

 

You have to realise that people do not react to information the same way you do. Just because you understand what a post means, does not mean the relevant OP will understand. 


In Topic: input in realtime.

Today, 05:00 AM

You will never be able to get real-time input from any Windows operating system, as these are not real-time operating systems (RTOS). Windows lets you get keyboard presses and depresses as events (and you can also get the internal timer value for when this happened) as window messages sent to a window, or to get the state of the keys (pressed or not) at any time. It's up to you to use all of these in such a way that the user thinks everything is happening in real-time.

 

Also, console programs are a bit different, as they put the key events into an input buffer that you can read from, and in this case, I don't think you can get the timer value for when the event happened...

 

Since you haven't specified what sort of program you are writing (console or GUI), the question still remains too broad for us to give you a straight answer.

 

Every time I see a "realtime" thread, one moronic wannabe just shows up trying to make the OP feel as stupid as possible.

It is incredibly obvious that the OP is a beginner, and doesn't need actual realtime input.

 

Edit:

Lol at the downvotes. I'm speaking the damn truth. It's okay to mention that realtime isn't the correct term.

However: "omg but realtime is not possible on Windows" etc... that is the kind of attitude that I am talking about here.

Why not just casually mention it and move on to actually answering the question?

Don't just treat the topic as if it actually is something else than what the OP intended.


In Topic: Explore 100'000 stars

27 September 2014 - 05:11 PM

Lmao, after like 2-3 minutes, the graphics driver crashed.

It's pretty cool though.


In Topic: Would you Still Play Nintendo 64-Quality Games?

01 September 2014 - 12:35 AM

This game was perfect. PERFECT! OKAY?

 

final-fantasy-mystic-quest-02.png


In Topic: MMO Four-in-a-row

31 August 2014 - 04:44 PM

Sounds like a fairly simple task relative to other game projects out there.

 

HTML, CSS, JavaScript and PHP should be enough to make this work.

 

The project can probably be accomplished on a $25k budget. You will have to think about graphics design and marketing as well though.

 

I might have misunderstood something, but this sounds like a game that you can create during a Ludum Dare, lol.


PARTNERS