I am new to SimHub overlays and to your work, but it seems so impressive I had to try it out! Thanks for creating and sharing. Is this an expected situation/message?
Thank you, really appriecate the feedback. Yes this is normal, once you use a certain width or heigth with an overlay Simhub shows this message but you can totally ignore it
Thanks--I got it all working! What an awesome feature with the multi-class standings--they show up as many as needed, or not at all if you are running single class. This is perfection for preserving screen real estate. Speaking of...the multi-function overlay is also awesome for that purpose. The only thing left I can see that would make it perfect is to include a weather forecast page (with the same info, but better presented, as exists in the Reiza HUD widget). In-game time, air and track temps, track state, wind info and forecast of what's coming would be incredible. Here's an example of one (for ACC) with less info, but very pleasant aesthetics. I really like the forecast using in-game time for the slots. Not sure what AMS 2 provides (perhaps nothing?), but an extra forecast slot an hour out to complement the 30 minutes and 10 minutes would be perfect in my opinion.
Sadly forecast information is not in shared memory, along with several other useful parameters. However I agree, the ability to make this kind of custom implementation is brilliant. Have had simhub for just over a year and what can be achieved with a bit of JavaScript and imagination is practically unlimited, that is, if the shared memory contains the data...
Yes, @CasteWand is right, at the moment the informations of Reizas new weather widget like weather forecast or in-game date and time of day is not available in shared memory yet. I really hope Reiza will add this in the future along as other useful informations like tire and fuel data of every car on the grid (since so man real life classes have this data available), so this data could be implemented into the overlays. Right now there is sadly no way to get this data or build workarounds to get them. But be sure if it get's added to Shared Memory, I will instantly start working on adding it
Great news!! One last quick question--do any of the GS plugin settings matter? I notice they are all off by default and assume that's OK?
I think they shouldn't make a difference since they shouldn't modify the data I'm using from the plugin in the coding. but honestly I never played around with the settings
Thanks for the reply--I will also ignore them! One last question: I love the visual design of your Tire Monitor 1.3. Are the colour gradients based on a generic scale, or can they react to different tire types like the widget in the game? For example, some of the rain tires overheat at temperatures that a slick is barely warmed up. ...Not sure if this is another area where the shared data does not include the tire temp ranges so a proper gradient can be displayed...
Right now the colors are customly tuned to match the color in the AMS2 widget with modern slicks. You are right other tires might use a slightly different color scaling, never really thought about that honestly since I rarely drive in the rain. Since there is no real data to use here how color scaling in the AMS2 widget works it has to be figured out by hand. I will write it down as possible adjustment for upcoming versions
It will be very complicated as every tire in the game has its own temp ranges. The rain tires are the most obviously different, but when there is everything from 1960's treaded tires to 2025 F1-grade slicks, you can imagine...
Your work has been very helpful to me, if you want, I'll PM you the JavaScript and ranges I use for wets... Tell me about it! Have been building my own dash and tyre/fuel strategy app in simhub. Slowly guestimating the ranges class by class for tyre temp colour gradients using the in game widget as a guide. A royal pita that shared memory doesn't contain the data. Along with weather forecast, ignition state, opponent tyres, accurate lap counts in practice and quali (doesn't count out and in laps so built my own), coolant/oil temp ranges, downforce load... The list goes on and on!
