Well I'm sure you know what logarithms and natural logs are, their use in MMF2 is probably usually relegated to non-game applications, but I bet you they have uses in physics engines.
V-sync I think is an old feature on some CRT monitors that prevents screen tearing.
Never condition... I've only used for testing. I don't think it can prevent events from happening, but I've never tried.
Clipboard I assume would copy things to the windows clipboard. O_o
A Clipboard object? Never used it! But I imagine its just a way of getting data from MMF into another app, say if you place an MMF string into it then you could paste that into another app (Notepad, Wordpad etc). If thats how it works I wouldn't use it in place of global strings or values.
V-Sync isn't just an old problem, it prevents screen tearing in any game however its a bit of a performance hog. I don't think it will affect most MMF games though and its worth enabling.
Never event is just that. It stops an event from working, good for testing but I don't think it serves any purpose for finished games/apps.
I never heard of the "windows clipbord" before. If I would, I wouldn't have asked. But after testing it, that's indeed what it does; let you communicate between two apps.
@ Dr.James: It's not an object, it's in the special conditions.
About log and ln, I don't remember learning these at school. I want to learn what they do now, cause I too am sure that it can get usefull. Will check for that tonight.
The Windows Clipboard is essentially where data is stored when you press Copy (Ctrl+C) in most applications. So the Clipboard object is useful for giving the user something to paste elsewhere, like in Word or an e-mail or something.
Quick crash course in logs... they're the opposite of exponents. Take for example:
2^3 = 8
That's an exponential equation. The logarithmic equivalent takes the output (8 in this case) and makes it the input, and also flips the input (3) to be the output. The base (2) stays the same. So it would be:
log(base 2)8 = 3.
You write the base as a subscript. It seems weird, but if you just keep seeing examples it works. It's almost akin to thinking in 4D.
ln is the natural log, which is log(base e)x.
If that made no sense, then know I'm no math teacher. They're good for calculus and stats.
v-sync has only ever worked on my machine, on other machines the game just runs slow with tearing.
It depends on the video card really. Some cards have a v-sync switch in their properties, so I figure if v-sync is really that important to someone they can just turn it on themselves.
@ OldManClayton
I read a bit more about the subject, and I don't know if you ever tried MMF's log, but it appears to have a fixed based, since it doesn't ask for two values. The base is probably 10 since i've read that it's used alot by mathematicians.
If I'm right, it couldn't be used in MMF, the way you said to.
But I've found that to find the X from this operation:
Value1^X = Value2
You can do this:
Ln(Value2)/Ln(Value1)= X
-or-
Log(Value2)/Log(Value1)= X
It seems to be something you learn to use, but don't need to understand why it works.
Logs are pretty awesome, except when they become imaginary and grow branches. That is the bane of my life right now
Yeah, log(X) gives log(base 10)N. All logs are assumed to be base 10, especially the ones in computers.
If you want say, log(base 3)N or something like that, you do log(X)/log(3).
You got the concept right there, Sקɪтzпαɢʟ. And you're also very right in that you don't need to understand why it works
Uses of log in klik:
- When you have 3^x and want to find x
- Using it as a damper, like if you have a power-up that gets much, much weaker for every power-up you collect. But it's very powerful.. say, if you have something that does 10000 damage, log(damage) will lower it to 3.
V-sync is supposed to make sure everything on screen gets synchronized. It's not exactly synchronized, the screen just displays stuff as fast as in can. V-sync makes them display everything at the same time, top to bottom. Problem is.. since it's displaying everything at the same time and slowing down to a rate where it can do so, it would actually look more choppy.
So, don't turn it on unless you notice it being out of sync. Not even when you think it looks out of sync, only when you know it is
I think the never condition was made at the time they made the always condition and thought, "Hey, if people are going to use Always, someone could also use a Never". I use it for debugging.. it's cleaner than deleting an event. You can just delete the Never if you don't need it later, instead of having to undo a delete.
Edited by Muz
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.