-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Electron Window opens, yet, NO Forza data transmitting to window. #70
Comments
Hi Jeremy, thank you very much for looking into this. I am using the "Car Dash" format (Data Out Packet Format) on my FM settings. I will check that file. Again, thank you! ====================== |
Just realized you were talking about the project you pulled together, and not what Austin has developed which is what I am currently using. However, does seem your pulling together some pretty cool stuff for the "backend" in order to get access to the Telemetry data. Thanks! |
I'm so sorry I got myself a bit mixed up. I was thinking that I had branched from Austin's project so assumed my work of getting it running with FM8 would work for you. My project is actually python based rather than JS and C based but I believe the issue remains the same. FM8 changed the data packet format and added 5 new values to the dash output packet. It appears that Austin already made a switch for this new format in the code but I don't see the new values available in the dataPacket class. Here are the new values directly from the Forza data out documentation Looking at Austin's code the data packet formatting ends at the driving assist lines even when under the new FM8 format @austinbaccus please let us know if we are off base or are missing something here. |
Thanks Jeremy! Your response explains it spot on! I will take a look this file and edit for some testing. Will let you know if it works. I am also wondering if these 5 new data elements are also set somewhere else. |
It appears that there is also data packet information in the following files
I would venture to guess you would need to add similar lines in each of those files to get it running. However, being unfamiliar with cs I'm a bit unsure of where else to dig for dependencies. |
I will give that a try, thank you! I am also unfamiliar with cs.....just learning & troubleshooting. *** Update: I added the additional missing code lines to both files (FMData.cs & Program.cs), yet, still with the same problem as described in mu first post. And, *.csv file capturing the "live" telemetry is empty (only headers). I'll keep researching (my friend Google) to see if there is something I can do to get rid of those errors, then, be able to focus on the telemetry data in & out to the *csv file. |
Describe the bug
. Add a , or to your code to match the DOM tree generated by the browser." at Line 67 of the "react-dom.development.js" file inside the "react-dom/cjs" directory.The Electron window opens with all the elements within the window, yet, when I check on the "View/Toggle Developer Tools", it provides and error of "react-dom.development.js:67 Warning: validateDOMNesting(...): cannot appear as a child of
I have not been able to figure this issue out, though I spent much time with my friend Google..lol...!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A expect that the data from Forza would be transmitted to and rendered by Electron.
Screenshots
Desktop (please complete the following information):
Additional context
I have used the RECORD button on the Electron window, yet, when I go to the *.csv file, only the titles of the Data Out from Forza are within the file (thus, no data). Not sure if the error explained above will address this data receiving/recording part of the SW package.
The text was updated successfully, but these errors were encountered: