Not quite. What gsync/freesync do is allow the monitor to be notified of when a frame has been produced, and trigger a swap exactly then. That doesn't mean that all frames are displayed for an equal amount of time.
Sure, it means that if one frame is late, it doesn't wait until the next vertical blank, but it does still mean that the previous frame is on screen for longer. If for example, a series of frames takes 12,14,30, and 16 ms to render, normally you'll see the frame before first for 16ms, the next for 16, the next for 33, the next for 16, etc. With gsync, you'll see them for 12ms, 14ms, 30ms and 16ms respectively. That's still jittery, just not as jittery.
The effect of showing some frames for 16ms and others for 33ms (what will happen if your game is running at somewhere between 30 and 60 fps) is much more jarring to you than the effect of showing all frames for 42ms.
This is why hitting 60fps (or slightly above) is the magic number at which it all looks smooth again - at that point, all frames are rendered before the screen refreshes, and you get an absolutely smooth 60fps with 16ms frame times across the board. The reason you ideally want to be slightly above 60fps, is because some frames will always takes slightly longer to render than others, you want even those to be rendered before the screen refresh.
Hint: there are bad solutions to this, like blending with the previous frame, and there are really really expensive solutions to this, like figuring out the paths things moved over during the frame, and rendering along those paths.
Aside - games have a much bigger problem than motion blur. Movies run at a consistent 24fps, no matter what. Games meanwhile takes varying amounts of CPU and GPU time per frame, and have fixed time windows in which a frame must have been prepared. If that fixed time window is missed, the same frame gets presented twice (or at frame rates like 24fps 3-4 times), the effect of showing some frames form 16ms others for 33ms, still more for 50ms, and still more for 66ms is much more jarring than the effect of consistently showing all frames for 42ms.
No, 2 seconds is not going to be an "eventful" stop from 35mph. 0.8 seconds is an "eventful" stop from 35mph. You could stop in less than half the distance to the lights in that time.
What you're attempting to assert is that it's impossible to stop safely for a red light when you get an orange. This is clearly false, millions of people do it successfully every day.
I would guess that it's theoretical because it involves things like knowing exactly where the JVM is positioned in physical memory, and how its pages are laid out. That, and that the demonstration involved knowing all of these things before you started.
2.4GHz is a band in which all radio communications are authorised by the FCC as long as they stay within certain limits. One of those limits is that they don't interfere with other radio communications.
Prior art (what you are seeking) is only one way for a patent to be ruled invalid. Being obvious (anyone would have thought of pricing for supply and demand as the most idiotically simple thing you could do) is another.
Though, since you want prior art, it's well known that supermarkets dynamically adjust the price of different items in different shops based on the demand at that time and location.
At 30 mph your braking time (the time between slamming the brakes on and you stopping) is 1.8 seconds. Reaction time varies, but depending on circumstances it usually is between half a second and a second.
At 55 we're already at well over 2.5s for braking alone, without reaction time.
Don't just pull numbers out of your ass.
1) The amount of energy at 55mph is roughly 5 times higher than at 30mph, given that brakes dissipate a fairly constant amount of energy at all speeds, that means your braking time at 55 is 5 times that at 30. 2) Thankfully, that doesn't mean your braking time at 55 is 9 seconds for an emergency stop. That's because your figure for 30mph is bullshit. The actual braking time for an emergency stop from 30mph is 0.8 seconds, and at 55, roughly 4 seconds.
All this put together means that when you're presented with a 4 second orange at 30mph, and you have to do an emergency stop, that basically means you fucked around for 2.8 seconds. That is, the 4 seconds is made up of 0.5 seconds of reaction time, 2.8 seconds of fucking around doing nothing at all, and then 0.8 seconds of actually stopping. As I said before - if you're failing to stop for a red when given a warning with an orange, you're driving dangerously.
Note, this can be observed in every day life. It's trivial to test, you approach some lights at the speed limit. When they turn orange, you start to gently brake for the lights. Observe that you come to a stop before the lights even turn red.
If you spend 3 seconds not looking in front of you in a car, you're driving dangerously to start with. Count out 3 seconds in your head, and consider closing your eyes for that long while driving - you'll realise it's a really long time. In reality, people glance away at instruments/mirrors for 100ms at a time, not 3 seconds at a time.
Are you suggesting that we simply list the professions that are allowed to have a genuine focused laser? If so, what happens when a spargeborgler (some new profession that critically relies on focused lasers) comes along? These laws always take years to get updated, leave horrible loop holes, and leave some people with genuine need out on the cold. If you can't express a general way to separate the groups, and have to revert to listing specifics, you're probably doing it wrong.
The problem is, by making systems where software is the last line of defence against damage, you typically can make much more efficient systems. Note car engines that use variable valve timing can damage themselves (e.g. by opening the valve during combustion, and allowing exhaust/plasma to back flow into the injectors), but they're much much more efficient than engines with a cam rod.
Never type that again. Seriously - vocalizing your pauses when speaking is bad enough, but there's no excuse when writing.
Actually, it's not "bad enough", it's an important part of speech. A pause, with a confused look on your face, and an "uhhh" noise conveys information, in fact, often, more than a whole sentence. I don't see any reason why conveying that sort of information concisely in one word should not be part of written english too.
You make this comment in jest, but seriously, I genuinely have had a conversation on a phone that started pretty much with "Hi there, I'm Barry and I'm calling from inside your Windows. I'm trapped in here and I need your password to get out."
They did if they were expecting a standard yellow light, then it changed red in 2.5 seconds instead of the federal minimum of 3 seconds and slammed on the brakes to avoid running the red light.
If your decision to brake or not was based on "I'm 2.5 seconds away from the junction, and that yellow has to show for 3", then you're driving dangerously.
To continue on my above comment (which I shouldn't have clicked submit on so quickly)... What could change to give you more leeway is that you could stop the opposing flow going green the very moment that one flow of traffic goes red. In the UK, the sequence for current, and opposing traffic in pairs goes (green, red), (yellow, red), (red, red), (red, yellow), (red, green) - that extra gap where neither direction has even a yellow, and then where the traffic that's about to start is shown yellow, allows people to relax and stop barging through so much.
Speaking as someone coming from the UK, the idea that the federal guidelines for yellows are too short is laughable. You guys get roughly twice as long on yellow as we do in the UK. I'd actually argue that the guidelines are too long. The very long yellow light times encourage people to think "it's okay, I can make it through". Meanwhile, yellow merely being a warning "red is coming, you'd better stop" makes things much safer.
I don't care what point you are trying to make, but when you start to victim blame, you lose credence.
What are you talking about? No one forced you to slam your brakes on at the last second. There's no victim here, there's no person forcing you into it. In order to be victimised you need to have someone making you a victim, and that person doesn't exist.
All OP is doing is blaming the person at fault - that is, the person who's taken longer than 4 seconds to make the decision to gently brake for a red light, when given plenty of warning by a yellow.
Given that you have 4-5 (depending on speed) seconds of yellow, there's absolutely no excuse to slam on the brakes. As OP said - the dangerous driving is entirely independent of the lights.
You really don't understand how TLS works if you think it doesn't protect you from someone injecting data into a stream, or from redirecting one to an unexpected endpoint.
Agreed! Who could be against the FCC regulating the internet? Nutters and Koch brothers types, that's who! I look forward to the FCC getting it's mitts deeply into the regulation of the interntet. I mean, how else can I be sure of getting cheap, fast pings for my games if not by getting the feds involved? My freedom to ping REQUIRES laws, bureaucrats, agents, and harsh penalties to ANYONE who fucks with my pings!
Given that all a lack of the FCC being involved has got you is a Comcast/Time Warner monopoly, prices 2-3 times as high as the other side of the atlantic, service an order of magnitude slower than the other side of the atlantic, and double charging both the sender and receiver for data... YES, FUCKING AMEN, WHO THE FUCK COULD BE AGAINST GETTING THE FCC INVOLVED!
The real question is, what does an average average californian rainfall look like. Sure, SJ got a lot last thursday and is continuing to get a bunch, but how does that small area average out with the rest of CA?
Slashdot Mirror
Not quite. What gsync/freesync do is allow the monitor to be notified of when a frame has been produced, and trigger a swap exactly then. That doesn't mean that all frames are displayed for an equal amount of time.
Sure, it means that if one frame is late, it doesn't wait until the next vertical blank, but it does still mean that the previous frame is on screen for longer. If for example, a series of frames takes 12,14,30, and 16 ms to render, normally you'll see the frame before first for 16ms, the next for 16, the next for 33, the next for 16, etc. With gsync, you'll see them for 12ms, 14ms, 30ms and 16ms respectively. That's still jittery, just not as jittery.
Simple - game frame rates aren't consistent.
The effect of showing some frames for 16ms and others for 33ms (what will happen if your game is running at somewhere between 30 and 60 fps) is much more jarring to you than the effect of showing all frames for 42ms.
This is why hitting 60fps (or slightly above) is the magic number at which it all looks smooth again - at that point, all frames are rendered before the screen refreshes, and you get an absolutely smooth 60fps with 16ms frame times across the board. The reason you ideally want to be slightly above 60fps, is because some frames will always takes slightly longer to render than others, you want even those to be rendered before the screen refresh.
Suggest a technique for doing it then.
Hint: there are bad solutions to this, like blending with the previous frame, and there are really really expensive solutions to this, like figuring out the paths things moved over during the frame, and rendering along those paths.
Aside - games have a much bigger problem than motion blur. Movies run at a consistent 24fps, no matter what. Games meanwhile takes varying amounts of CPU and GPU time per frame, and have fixed time windows in which a frame must have been prepared. If that fixed time window is missed, the same frame gets presented twice (or at frame rates like 24fps 3-4 times), the effect of showing some frames form 16ms others for 33ms, still more for 50ms, and still more for 66ms is much more jarring than the effect of consistently showing all frames for 42ms.
No, 2 seconds is not going to be an "eventful" stop from 35mph. 0.8 seconds is an "eventful" stop from 35mph. You could stop in less than half the distance to the lights in that time.
What you're attempting to assert is that it's impossible to stop safely for a red light when you get an orange. This is clearly false, millions of people do it successfully every day.
I would guess that it's theoretical because it involves things like knowing exactly where the JVM is positioned in physical memory, and how its pages are laid out. That, and that the demonstration involved knowing all of these things before you started.
2.4GHz is a band in which all radio communications are authorised by the FCC as long as they stay within certain limits. One of those limits is that they don't interfere with other radio communications.
Prior art (what you are seeking) is only one way for a patent to be ruled invalid. Being obvious (anyone would have thought of pricing for supply and demand as the most idiotically simple thing you could do) is another.
Though, since you want prior art, it's well known that supermarkets dynamically adjust the price of different items in different shops based on the demand at that time and location.
So... don't brake the law, and you won't get a $300 ticket... It's that easy.
At 30 mph your braking time (the time between slamming the brakes on and you stopping) is 1.8 seconds. Reaction time varies, but depending on circumstances it usually is between half a second and a second.
At 55 we're already at well over 2.5s for braking alone, without reaction time.
Don't just pull numbers out of your ass.
1) The amount of energy at 55mph is roughly 5 times higher than at 30mph, given that brakes dissipate a fairly constant amount of energy at all speeds, that means your braking time at 55 is 5 times that at 30.
2) Thankfully, that doesn't mean your braking time at 55 is 9 seconds for an emergency stop. That's because your figure for 30mph is bullshit. The actual braking time for an emergency stop from 30mph is 0.8 seconds, and at 55, roughly 4 seconds.
All this put together means that when you're presented with a 4 second orange at 30mph, and you have to do an emergency stop, that basically means you fucked around for 2.8 seconds. That is, the 4 seconds is made up of 0.5 seconds of reaction time, 2.8 seconds of fucking around doing nothing at all, and then 0.8 seconds of actually stopping. As I said before - if you're failing to stop for a red when given a warning with an orange, you're driving dangerously.
Note, this can be observed in every day life. It's trivial to test, you approach some lights at the speed limit. When they turn orange, you start to gently brake for the lights. Observe that you come to a stop before the lights even turn red.
If you spend 3 seconds not looking in front of you in a car, you're driving dangerously to start with. Count out 3 seconds in your head, and consider closing your eyes for that long while driving - you'll realise it's a really long time. In reality, people glance away at instruments/mirrors for 100ms at a time, not 3 seconds at a time.
Are you suggesting that we simply list the professions that are allowed to have a genuine focused laser? If so, what happens when a spargeborgler (some new profession that critically relies on focused lasers) comes along? These laws always take years to get updated, leave horrible loop holes, and leave some people with genuine need out on the cold. If you can't express a general way to separate the groups, and have to revert to listing specifics, you're probably doing it wrong.
The problem is, by making systems where software is the last line of defence against damage, you typically can make much more efficient systems. Note car engines that use variable valve timing can damage themselves (e.g. by opening the valve during combustion, and allowing exhaust/plasma to back flow into the injectors), but they're much much more efficient than engines with a cam rod.
Never type that again. Seriously - vocalizing your pauses when speaking is bad enough, but there's no excuse when writing.
Actually, it's not "bad enough", it's an important part of speech. A pause, with a confused look on your face, and an "uhhh" noise conveys information, in fact, often, more than a whole sentence. I don't see any reason why conveying that sort of information concisely in one word should not be part of written english too.
You make this comment in jest, but seriously, I genuinely have had a conversation on a phone that started pretty much with "Hi there, I'm Barry and I'm calling from inside your Windows. I'm trapped in here and I need your password to get out."
Because I will slam the brakes to stop. NO matter what. No matter how fast I am.
That's the point - if you're going so fast that you need to slam the brakes on, then you were already driving dangerously. Stop that, now.
They did if they were expecting a standard yellow light, then it changed red in 2.5 seconds instead of the federal minimum of 3 seconds and slammed on the brakes to avoid running the red light.
If your decision to brake or not was based on "I'm 2.5 seconds away from the junction, and that yellow has to show for 3", then you're driving dangerously.
To continue on my above comment (which I shouldn't have clicked submit on so quickly)... What could change to give you more leeway is that you could stop the opposing flow going green the very moment that one flow of traffic goes red. In the UK, the sequence for current, and opposing traffic in pairs goes (green, red), (yellow, red), (red, red), (red, yellow), (red, green) - that extra gap where neither direction has even a yellow, and then where the traffic that's about to start is shown yellow, allows people to relax and stop barging through so much.
Speaking as someone coming from the UK, the idea that the federal guidelines for yellows are too short is laughable. You guys get roughly twice as long on yellow as we do in the UK. I'd actually argue that the guidelines are too long . The very long yellow light times encourage people to think "it's okay, I can make it through". Meanwhile, yellow merely being a warning "red is coming, you'd better stop" makes things much safer.
I don't care what point you are trying to make, but when you start to victim blame, you lose credence.
What are you talking about? No one forced you to slam your brakes on at the last second. There's no victim here, there's no person forcing you into it. In order to be victimised you need to have someone making you a victim, and that person doesn't exist.
All OP is doing is blaming the person at fault - that is, the person who's taken longer than 4 seconds to make the decision to gently brake for a red light, when given plenty of warning by a yellow.
Given that you have 4-5 (depending on speed) seconds of yellow, there's absolutely no excuse to slam on the brakes. As OP said - the dangerous driving is entirely independent of the lights.
before you insert race on this, know that red light cameras are basicly a tax that hits the city's poorest residents the hardest.
Huh? Are you asserting that there's some causal link between being poor and running red lights?
You would complain to Microsoft because the scammers introduce themselves as "calling from Windows" or "calling from Microsoft".
You really don't understand how TLS works if you think it doesn't protect you from someone injecting data into a stream, or from redirecting one to an unexpected endpoint.
Agreed! Who could be against the FCC regulating the internet? Nutters and Koch brothers types, that's who! I look forward to the FCC getting it's mitts deeply into the regulation of the interntet. I mean, how else can I be sure of getting cheap, fast pings for my games if not by getting the feds involved? My freedom to ping REQUIRES laws, bureaucrats, agents, and harsh penalties to ANYONE who fucks with my pings!
Given that all a lack of the FCC being involved has got you is a Comcast/Time Warner monopoly, prices 2-3 times as high as the other side of the atlantic, service an order of magnitude slower than the other side of the atlantic, and double charging both the sender and receiver for data... YES, FUCKING AMEN, WHO THE FUCK COULD BE AGAINST GETTING THE FCC INVOLVED!
The real question is, what does an average average californian rainfall look like. Sure, SJ got a lot last thursday and is continuing to get a bunch, but how does that small area average out with the rest of CA?