Ayup fella, I had a quick look at this (long long overdue). The recording stuff is really helpful, but I can't get the viewer stuff to run. I do some recording, then I invoke the view with r3e-trace-viewer.exe trace_[....].r3t. It falls over straight away on a Glew assertion: EXT_direct_state_access support required Line 487 of r3e-trace-viewer.lua - assert(gl.__GLEW_EXT_direct_state_access ~=0, "EXT_direct_state_access support required")
Oh, and I took out the assert line and it barfed later on (don't have the error message). This is with an AMD r9 280, 15.7 drivers, win7 64bit
Heh, don't worry about that. I swore I'd never buy another ati card after the shocking drivers for the original Radeon 256. I thought things might have improved after more than 10 years. Of course, they bloody haven't
Computer says "no"... This now fails: progTrack = glu.loadprogram({ GL_VERTEX_SHADER = "shaders/track.vert.glsl", GL_FRAGMENT_SHADER = "shaders/track.frag.glsl", }) assert(progTrack, "could not load shaders/track") r3e-trace-viewer.lua line 563. So I guess it can't even load the shaders Of all my recent unwise purchasing decisions, buying an AMD graphics card was easily the most retarded
Hi pixeljetstream! Is it possible that your exported .csv was compatible with telemetry software like Atlas Express (or similar)? It would be very interesting to export all data and turns into one file how does Motec Plugin in other sims... Thanks for your works!
Bah, can't get 'em away from the telly. Bloody kids. Still, it's given me a chance to have a quick test and the app now works. Yay
@Vojvoda if you can attach a sample file of the format you want to have, I can see what I can do. Btw the whole app is scripted, the exe files do more or less nothing, you could mess with the "saveCSV" function yourself https://github.com/pixeljetstream/r3e-trace-analysis/blob/master/r3e-trace-viewer.lua#L133
@pixeljetstream CSV file it's attached, is a "formation lap" with FR35 in rF2. Many thanks! Note: Uncompressed file size is 31.017 KB
Lots of new features and some fixes. Thanks to @Vojvoda for feedback. The CSV formating was changed to be easier importable by other tools and one can save the entire session (one or multiple trace files) as single big csv file, whose "time" will be treated continuously. The biggest visible change is that the ui is now made of dockable windows, which allows free customization of the app and is the first necessary step to allow new graph views. Intended are line and bar graphs as well as 2d scatter plot. Settings stored in ini file (window layout...) /AppData/RaceTraceViewer.ini Customizable UI (dockable windows) New file menu entry to store entire session with all properties as csv No longer print values as vectors, better to work with X,Y,Z properties "config.viewer.convertvalues" (default:true) to convert radians to degrees and m/s to km/h Statistics for properties (lap min, max, average) as well as gradient display Bug fixes (pan, range) The new graphs will be a bit more work, so the next feature will be custom calculated properties. Which will allow people to create new properties from others by scripting how they should be calculated.
Hi @pixeljetstream ! Please... Could you do a "guide for dummies" to update LUA for all (latest) data in shared memory? I have done some testing but I have not been able to make it work... https://github.com/sector3studios/r3e-api/commit/ffddb2989d76472cf88a77eebadd6170f28d8cc2 I'm interested in some data to Atlas Telemetry. Thanks in advance!!!
This is so awesome just what I been looking for I'll try it out right away thank you for all your work you put in to this
Thanks @Vojvoda will look into it end of the week. I will not store the "all drivers" data for tracing, as it would waste a lot of memory and it's not really useful for sake of telemetry given the way the data is organized. From glancing over your diff, I didn't see an error on your end. I've just pushed some small changes to allow loading of older files.