euxx

I am still not certain what the problem is... I don't recall any changes between those versions in the stage editing or export/import to ezws. BTW, after importing stages to PS, do you see classifier checkbox and classifier id on stage editing screen? Could you also remind me what "EzWin to PractiScore utility" you're referred to?

CHA-LEE, what PS version are you running? Is there anything I need to look at at PS side? Not sure about conversion tools other folks developed and what kind of issues are there with new PS versions.

If they are bad, we really need to hear more than that. Please provide details, so we can make PractiScore better. I'd always recommend the last version, as it has fixes for critical issues reported to us. Though it is generally a good idea to test functionality before real match. We do what we can for each release, but we can only do so much and could use some volunteers who can help to test release candidates. If anyone is interested, please email support@practiscore.com and state what devices you have and what match types can you test. It would be a big help for us.

For those running Nook 1.2.1 update, we just posted Android version 1.1.2 that fixes issue with numeric keyboard. Special thanks to Chris who mailed me sd card to allow to reproduce and debug this issue.

Mark, this usually happen when side-install app that was previously installed from Google Play and vice versa. Uninstalling should help (though you'll loose local competitor's history if that's your primary device for registering competitors).

Please update to 1.1.1, which fixes a crash on opening match results and also allows custom penalties. Updated application can be downloaded from PS web site.

If you are using timeplus matches on Android and updated to 1.1.0 (with IDPA support), please update to 1.1.1, which fixes a crash on opening match results. It can be downloaded from PS web site.

Yes it does. Android version can be also synced with iOS.

We just posted PractiScore 1.1.0 for Android to https://practiscore.com/ It should appear in Google Play in a next few days. As before, you can send your feedback and report issues to support@practiscore.com or into PS issue tracker at https://practiscore.com/bugs/ This version introduces IDPA support on Android. Please give it a try and let us know what you think. The main difference from iOS version - "points down" entry is on the same screen as times. There is also a fix for an 1.0.17 version app crash reported by several users.

You may want this quote from developer of official IPSC scoring software: --- Aeon Innovation™ is a Microsoft BizSpark startup company that provides competitive shooting sports scoring and statistics to the International Practical Shooting Confederation (IPSC), via its website and Windows-based programs. Its short-term vision is to facilitate distributed processing by provisioning an embedded webserver within its Windows-based client that performs networked scoring activities at the shooting range, and expanding its centralized webserver capabilities to provide interim and final match results as provided from the said client. Aeon Innovation™ intends to expand its offerings to accommodate additional shooting organizations and keep its competitors at bay. --- PS: Not sure why they want to keep me "at bay"

I am not sure where the PS Bug Tracker is. I sent an e-mail to the support address listed on the PractiScore website with my suggestions. https://practiscore.com/bugs/ You'll need to register

Cha-lee could you please enter those issues in PS bug tracker. I'll look at that on next iteration. Trying to convince Ken to ditch separate targets screen and score all on one screen, so it will be moo point to fix the target screen. BTW, the app does check completeness when review button taped on time entry screen, but I may have overlooked it on target scoring screen.

Can someone closely familiar with IDPA rules comment on this? Let's say there is a Vickers count multi-string stage. Mix of steel and paper (actually not sure if this will be a valid IDPA stage). Now the question. Is there any circumstances when steel or paper targets could get more than one FTN penalty? Here is the rule that confuses me: --- CoF 7. Any CoF that requires the shooter to re-engage a target in two (2) or more strings of fire MUST be scored Limited Vickers or scored and taped between strings. --- So, if on Vickers count stage, shooter received FTN on one of the targets and then target patched between strings. Will this shooter receive another FTN if he din't shoot enough points again on that target? Or, for example, missed the steel target again. I've been told, that normally, multi-string stages are shoot without patching paper between strings (and usually no one is using steel on such targets, and also use Limited Vickers on such stages). So, how FTN penalties would be assigned in this case? I'll appreciate your comments and thanks in advance.

Bob, there is also a need to support for IPSC Handgun, Shotgun and Rifle maches. The only question is which "burner" is on front of the other... PS: for the record I don't shoot IDPA, SC or MultiGun.

I will as soon as you get Steel Challenge implemented! Hey, uspsa is not sponsoring SC work.

So, who want to contact uspsa and request to change membership cards to have qrcode on them?

My prototype for Android is using 3rd party QRcode scanner app. So, you use that app to scan QRcode provided by competitor and it simply opens competitor editing screen in PractiScore already populated with all competitor data read from QRcode. We can also add a button to start QRcode scanner right from PS. It saves some taping on the touch screen when registering walk-in competitors. The main logistical issue here is to create those QRcodes for walk-in competitors. Competitors planning to walk in could use web site to create and print them at home. For frequent competitors, MD could pre-print QRcodes and hand them over at the match. We could also provide simple app to create those QRcodes right on Android and iPhone devices... Such app also can be used to enter competitor data and beam it to the master device used for registration over NFC or WiFi.

CHA-LEE, facelessman, thanks a lot for your comments. Most appreciated. At couple stages I messed up the foot work. On stage 3 I overrun too much back, missing single shooting position for 4 targets on the left. On stage 6 there wasn't foot shift, I just had a trigger finger freeze on the last target. I tried starting on the right on Stage 4, but it felt like too much running while shooting awkward targets on my right. The issue with reloads that facelessman mentioned, could have been mitigated by shooting those targets from far position, right after shooting one target on the far left behind palm trees. Good comments about all moving targets. Somehow I completely failed to figure them out before shooting. Though most of them were too fast for me to shoot reliably. Thanks again guys.

Bill, you are welcome to give your thoughts on keyboard issue in corresponding bug entry in Mantis issue tracker. I am not going to comment on it here.

Android 1.0.17 version is posted. You can get it from the web site, it should appear in play store in next few days. I recommend everyone using 1.0.16 update to this version. There are number of fixes for critical issues reported here and in PS bug tracker recently. You can find whole list on the web site or you can use long tap on version number text on the app main screen. PS i still dont have working nook 1.2.1 firmware, so no changes to keyboard issue. As a workaround use "hackers keyboard" app.

Thanks, lugnut. Stage 2 plan was real bad, and execution even worse. Stage 7 was the first one of the day and I figured about small poppers right after I shot the stage. From watching this again, it seem like my main struggles are shooting on the move, wide transitions, steel arrays and moving targets...

I know what you are talking about... I was under impression that my foot work is ahead of my reloads, but it seem like the opposite.

Shoot my 3rd Florida Open this year. Would appreciate any comments.

Most probably you removed your card without properly flushing all unsaved data and now some files are likely corrupted. Put your card in and run a "Check Disk" tool for corresponding device drive from Explorer on your PC. After you download file to SD card on your PC, you need to close Explorer folder and then right-click on USB icon and select corresponding Eject menu for your card. Eject menu should be also available on corresponding device drive in Explorer.

2nd trough 5th overall or in each class? How about people who couldn't stay for awards? Anyhow, that was a very impressive prize table and as always a great match.