With better data logging I would be able to see things like: what g-force was I seeing during the oil pressure dips? What direction was I turning? Was I braking? It would go a long way. I have no idea what turns/g-forces I was seeing in these logs. I had to decide between recording the runs with track-addict to grab g-force and video data vs using the OBD port and MHD to log the cars performance. Here is a basic comparison I did at a recent autocross.
But for some reason, photoshop seems to just keep loading and freezes, in other words, the nothing gets rendered and I need to force quit every single time.
RACERENDER FREZEES UP WHEN TIME TO RENDER VIDEO UPDATE
An Aimsolo or something like that is cool but not even close to being worth the expense for the average enthusiast. I've installed my photoshop to the recent update and I'm trying to render video for an animation I've created based on video layers, frames. It's still not a prefect solution but as of right now we don't really have any solution. With additional MHD channels I could then record with a separate camera and then add the data to the video later. I don't know the technical aspect of it, but, I do know that some of this data is not available through standard OBDII? It runs through the COM port? Steering angle, actual pedal angle instead of throttle angle, actual brake pressure/angle, x/y/z forces from the cars accelerator. I'd easily pay $50 or so for an "add-on" that unlocks a track-oriented pack of logging pids. I would just like to be able to be able to do basic data overlay when recording video. Relative to E-N55 MHD, there is still tons of other projects that need attention (Jake, that 2048 limiter needs your attention lol). doesn't seem like MHD has any intent on putting any effort into logging channels. You could set both to start logging at the same parameter effectively syncing them together. This also would be a good way to have MHD data synced with other loggers. It would be nice to have it start logging after a parameter was hit, say 3000 RPM or 60 MPH, neither of which of would happen in the paddock but would on pit exit as you head out on the track. Then there is the whole part of remembering to start logging in the first place, lol. Touch screens don't work well with driving gloves either. Network render farms have been in use since the early days of 3d animation and rendering, and video effects processing. Another option is to utilize multiple workstations for the same render as opposed to upgrading one workstation. This could be a good 5, sometimes 10 min of which you don't care to log anything. Now obviously this is the most expensive way to go about increasing your render speeds. You get all your gear on, get in the car, head to the grid, and start waiting for everything to go. Maybe it already does this or someone mentioned it and I missed it, but it would be nice if MHD had an auto start log function. Click to what is your take on additional analog sensor logging, in other words how many "slots" are there in the DME for adding 0-5v inputs?