Was trying to work with an online lesson this weekend, FSX 2020 could see the cameras, live video during setup was fine, using the Imaging Source DFK usb cameras, hitting on the range, FSX had no replay of any swings, just blank in the analysis view, nothing recorded. Any thoughts on why it wouldn't record? Had a Chrome browser running with Zoom open.
FSX 2020 Swing Cameras no Playback
Collapse
X
-
Tags: None
-
Was another program using the cameras at the same time by chance? I know that when I adjust the cameras using the IS software, I need to ensure the software is closed before I start FSX2020 or Play or I will have issues getting FSX to see the cameras.
-
Good thought. I was on a Zoom call at the same time, perhaps the Zoom program was controlling them, even though I was using the webcam for the call? I remember seeing the swing cams as an option when I first connected via the webcam with Zoom. Is there some way to restrict the Zoom call to just accessing the webcam?
-
-
Seems like if I just load FSX 2020 everything is fine. How can do a Zoom call using my Logitech Video Cam, but tell Zoom to ignore the Imaging SOurce cameras? Seems like as soon as I start a Zoom call it takes over all the cameras?
Comment
-
MongoOnlyPawn - have you set your default camera in Zoom? I think when you do this Zoom ignores any other camera inputs.
Comment
-
-
shoutout to Surfthing Computers who helped me out with my FSX 2020 issues with these exact imaging souce cameras. The likely culprit is that FSX loves to install old "graypoint" drivers which basically break everything with these cameras. They walked me through uninstalling those old drivers and getting the proper ones installed.
one warning: FSX 2020 is just not stable at all above 120 FPS. If you keep these nice cams at 120 fps it will probably work but don't expect the full 238FPS to work. I switched over to Swing Catalyst ($200/yr home edition subscription from foresight website)...
Comment
-
The Imaging Source cameras do indeed need the proper drivers - IIRC they are avail on the IS website. I have not had an issue with FSX installing any other drivers.Originally posted by frodaddy00 View Post...... issues with these exact imaging souce cameras. The likely culprit is that FSX loves to install old "graypoint" drivers which basically break everything with these cameras. They walked me through uninstalling those old drivers and getting the proper ones installed.
Comment
-
Not sure what's happening. I've got the IS drivers package installed per their website. Regardless of Zoom running or not, FSX will start up just fine, show both cameras operating at 120 fps, track the first shot, show the video, then both cameras lock up. On the "Video" tab in the analysis section you can watch the replay once, from one camera, then the "viewing" box turns white. No amount of fiddling with refresh rates, FPS or resolution get the cameras to come back online. If I restart FSX it's the same thing, everything is good for one shot, then nothing. This happens if I never start Zoom, so I don't think that's the culprit. Never had this problem with swing catalyst, but trying to use 2020 now for some online lessons, thus the change. Having friends over for adult beverages & a scramble today, might have some time to work on it tomorrow.
Comment
-
Hmm that's weird. I have not used FSX2020 for a bit (have been using Swing Catalyst) but will try it out later on today and let you know.
As an aside, can you list your computer specs and what cables you are using for your cameras? I am assuming you have swapped cables and that your computer is up to the task? Dual recording and Playback is pretty CPU/RAM intensive.
Also, this is a pretty decent thread (there are others) with camera optimization & setup which might help: 2021 Primer on Dual High-Speed Video Recording of a Golf Swing - Golf Simulator Forum
Comment
-
Windows 11, Asus ROG STRIX Z790-E Motherboard, Intel Core i7-13700 13th Gen CPU, Corsair 2x16 DDR5 7200 RAM, Corsair RMx 1200 Power Supply, Samsung 980 Pro M2 1TB SSD, Nvidia GeForce RTX 4090 FE GPU
I've reviewed the article referenced but will take another look at it. Thank you for the help.
Comment
-
Hmm, good question. I am using Imaging Source OEM cables, but will try to use separate connections.
Comment
-
jasonreg, thank you, using usb ports on different "buses" on the motherboard has alleviated the issue, at least as of 3 different trials! I looked up my motherboard specs and made sure I used ports that are not on the same "bus" or pathway to the system. Thank you for the idea.
Comment
-
Glad it worked out! There really is an awful lot of data flowing from these cameras - understandable the pip can get maxed out.Originally posted by MongoOnlyPawn View Postjasonreg, thank you, using usb ports on different "buses" on the motherboard has alleviated the issue, at least as of 3 different trials! I looked up my motherboard specs and made sure I used ports that are not on the same "bus" or pathway to the system. Thank you for the idea.
Enjoy!
Comment
Comment