LukeH

It sound like the firmware isn't running. In which case flicking the switch won't put it into programming mode anymore. Remove the two screws, open the back and press the reset button. Then try flashing the beta firmware again. If that doesn't work, try again with the normal firmware.

Hi Petite, Glad you like it. There is a newer version which I haven't posted publicly yet that has the changeable config option. I'll PM you a link.

There is a version of Flyblind that has the selectable config option. I'll pm you a download link.

Nicely summed up!

Hi, There is a new version that includes the latest speaking features from the official beta. You can download it here:FlyBlind20141219 Copy the audio folder to your Flysight after flashing the firmware and rename your old config file so a new one with the new options will be created.

I don't think so. I've tried it with Hyper-V and VirtualBox and with various USB over ethernet solutions but I haven't tried with VMWare. The problem is with Windows 8/8.1 loading the driver for the Flysight when the Flysight is in programming mode. Because the Win 8 host can't load the driver you can't pass it through to the VM. If you have some software that passes the entire USB controller through to the VM you might have a chance. Some sort of bootable DVD\USB stick with a different OS would probably be the easiest option.

It's by suit. Each model name is assigned to a category. It looks like some suits may be in the wrong category and everyone knows that some manufacturers make many different suits with the same model name stitched on them ;-) so perhaps two suits with the same or similar names shouldn't be in the same category. Some very experienced guys are cleverly staying in the lower categories meaning that the others have no chance. Smart but not very sporting.

Why the interest, are you the wingboard guy? https://www.kickstarter.com/projects/2138403030/wingboard-carve-the-sky

There results are attached. These competition figures are skewed because of the tactics element, diving and flaring etc. It looks like he nailed the timing of the flare round 1 so the score benefits from 25 seconds of boost. On round 2 the flare was a little premature so the peak wasn't included in the scoring window. The sustained GR after the flare looks to be about 2.5 on round 1 and 2.2 on round 2, both of which seem a bit on the low side for a (slight) tail wind. [inline 14535-Chart.png] [inline 14600-Chart.png]

Thanks. I was asking because many people seem to think that somewhere between 3:1 and 4:1 is readily achievable. A year or two ago I reckoned that 2.5-2.9 was a realistic figure, but was wondering if that has changed much. I've seen claims of sustained 3.1:1 and even 3.5:1, and a base jump with a mandatory 2.7:1 requirement (pretty hardcore if the skydiving world champion is only getting 2.7 with a slight tail wind) I guess it hasn't changed much, perhaps more people are now achieving the upper end of that range.

Where the distance runs done upwind?

There are two main versions of the Flysight hardware. If you have the version with the AT90USB646 chip try this version of Flyblind: https://dl.dropbox.com/u/13230955/FlyBlind-646-1.1e.hex If you are unable to get Flysight into programming mode, open the case and press the reset button.

Oh wait... you're right wingsuits have been flying up for years... https://vimeo.com/17074287 It's possible to build energy in a WS by diving and flare out to a temporary low fallrate, level flight or a small climb but it requires a significant dive and flare, just like any other wing. Where is the boogie man you've invented that is denies this? What you are trying to portray is that the smoke trail proves a climb, it doesn't. In your above video (which has the camera below and looking up), it's even clearer that it shows a turn towards and then away from the camera. "Fact: Camera on level" Really? Get your eyes tested. There are 3 possibilities, this is a windup, you are really dumb or you're just using this to promote false info knowing it's not true. I doubt you are that dumb, so I'd guess a combination of the other two.

Jeb, You posted before that the Recon HUD was giving you much higher speed readings than your Flysight. Without digging up the thread I think you were saying 140MPH from the goggles and 125MPH from Flysight and your feeling was that the Flysight figure was probably the correct one. What was the cause of such a big discrepancy and how has it been fixed? Could you describe the difference of what you are currently jumping from the standard goggles, and what further changes are they able to make, test and ship by the end of the year? As they won't know for a while if they have the 250 orders, it seems like a very tight time frame for development and testing...

Thanks for the sentiment and I'm glad we are on the same page. I'm not too worried about those that try to paint me as being negative or scornful, it's easier for them to do that than stick to the facts. Some people fall for it but in the end they usually make a tit of themselves.