Heya Everyone!

There should be an update soon to the TurnSignal beta that includes, among others things, a working bypass for the Steam 'Currently Playing' issue that has been reported by so, so, many people!

After the beta updates, if TurnSignal loads up the preference file and finds that SteamWorks is disabled, and also detects the argument '--steam' ( which is now given when launched from Steam by default ), it will launch a new instance then close itself using a method that lets it slip by Steam's auto-launch detection, and run un-tracked and unannounced, save for the unavoidable initial one on first launch ( I tried for every detection, but because Unity only executes after load, the time it takes is enough to be detected by Steam, sorry T>T ),

This also means that if the option is disabled, and its not launched through Steam, it should never attempt to connect until the option is enabled again,

Besides that, I've made a few other ( hopefully good ) performance changes;

• The Menu is now only rendered once for both places its displayed, the frame is now copied instead of rendered for the Overlay, which saves memory and CPU/GPU cycles.
  
  
• The floor Twister logic has been revisited and redone, the CPU / Memory bound math for the Bezier curves for the floor display has been rewritten to use Unity's 'Burst' compiler, which shakes down to assembly, taking its calculation time from around ~3.5ms to less than ~1ms ( on avg, on my system, numbers may vary )
  
  
• Went all over everything again, trying to reduce memory and CPU footprint, went from ~1-3% CPU and 85MB Ram, to >0.5% CPU and 60MB Ram,
  
  
• ( Not really a change ) Experimenting with the ILL2CPP compiler in Unity, have pretty much gotten it to work fully ( save for the tray Icon ), but performance is actually about the same, not a whole lot of work being done already, 90% of frame time is spent waiting as to not waste resources rendering above 90fps.

I've finally carved out some time, and have actually tested out the current beta in Pavlov for a bit, and it seems to work well enough, so look for it very soon!

Thank you all for the support and communication, and remember, if you have any Feedback, Questions, Comments, or Issues with TurnSignal, please feel free to let me know!

( PS: I've noted a lockup, only affecting TurnSignal itself, that I cannot seem to find the cause of. It happens seemingly randomly, I want to say it happens when you try and watch resource usage with Task Manager, but its hard to really know, since I do that about every launch when developing )

Heya!

Pushing an update to the beta because I got reports that errors in the beta could grow the log file to insane sizes, due to me misconfiguring some stuff with the build,

New version should fix this and the underlying config problem, and now checks the log files size every 10 seconds to see if its grown above 10 mb, and if so, should clear it, as a just in case.

The update should be out asap, so look for it!

Also, super big thanks to Heathen and FireWaran for the quick turnaround on reporting issues!


As always, Thank You for the support, and if you have any issues / feedback / questions, please feel free to let me know!

Heya!

So, its been a bit, over a year in fact, since I first started development on TurnSignal, and about 9 months since it was last updated, ( I can't believe I missed the anniversary ),

But no longer will it be that long!

I've been pulling super long nights to finally get time for development, and its finally payed off!

If you're brave and willing, and want to test the latest ( and hopefully greatest ) version of TurnSignal and its newest Turn Tracking algorithm, I've published a new build, 2.4.5, under the 'Beta' branch in the beta's tab!

( You can find this by right clicking "TurnSignal" in steam, selecting properties, navigating to the BETAS tab, and selecting 'beta' from the drop-down list )

This new build may look and feel visually similar to previous ones, but I've essentially re-built the entire underlying app, piece by piece, to be a bit more efficient, straightforward, and easier to develop on,

Here's a non-exhaustive list of changes;

• Refactored app code architecture; A major overhaul to the apps underlying code and logic.
  
  
• Updated OpenVR Lib ( need to re-update it again ).
  
  
• Updated Unity Version to latest non-beta (at time of writing this).
  
  
• Brand new tracking algorithm; no longer uses Gyro input, and should mathematically be more accurate ( maybe with some feedback tweaking ), save for the niche case of doing a "stop-drop-and-roll" procedure while wearing the headset.
  
  
• Updated the location of the options file to be in user appdata folder instead of root directory.
  
  
• Made "SteamWorks Optional" function actually work, the app can now be launched outside of Steam when set.
  Requires a restart to properly not-be-detected, and I still need to add a fix to disable it when launching from Steam.
  
  
• Completely rewrote OVRLay Unity Lib, ( the underlying Overlay library I wrote for TurnSignal ) to be more modular and straightforward ( this has its own github page I will update ).

... And more!

Lastly, Thank you all for the support thus far, any feedback you can give me from testing, or in general about the app, including if the tracking has improved or not, will only help make TurnSignal Better!

Thanks for reading!

PS: The reason this is a beta, and not a full release update, is that I've yet to even test it in a game, pretty much 100% of my free time lately has been working at work, then working on TurnSignal. While I've tested throwing the headset around, and spinning circles in SteamVR Home, I have no idea how it might perform in niche situations or not, so until then, its a beta!

Heya Everyone!

This is just a small radio-burst to let you know that I'm still alive and kicking, and while I've been a bit busy lately with a new Job, Family stuff, the general mishmash of humanity we all face;

TurnSignal is far from dead or abandoned, and I have heard and am doing my best to address the concerns and feedback the community (you guys!) have brought fourth, including (but not limited to, and in soft priority order);

• WMR Support (This is actually a bug as they should function through SteamVR, but GOOD NEWS: I got a Lenovo Explorer just so I could test and fix this issue!),
  
  
• Drift (Inaccuracy that builds the longer you play),
  
  
• Accurately / Inaccurately showing usage / play time (Several people prefer it be silent in Steam game history),
  
  
• Performance (I'm having trouble pin-pointing an exact cause, it doesn't seem hardware based, which makes me think it’s some sort of rare config or state that can nuke performance),
  
  
• More Options (More things you can change / edit in settings),

Again, this is not a complete, nor finalized priority, list, and most of these features / upgrades will probably be trickled out over several smaller updates (No reason to make people wait and to make testing harder),

So, yeah! Just a heads up I'm not dead, TurnSignal is not forgotten or unloved, and I really appreciate all the love and feedback you guys have given! Its more than I could have every hoped for, and you've made this whole project an amazing experience to work on!

Thank you!

TurnSignal 2.4.0 Has Been Released!

Includes a new Follow Player Headset option that makes the Flower / Floor Overlay, well, follow the player! (Also includes a Follow Speed slider for tweaking it to your preference)

This release also includes, yet ANOTHER, improved algorithm (and yEt aNOTHEr in the pipe).

So, hopefully, that won't break anything, but it might, so get your bug-reporters ready.

As always, feel free to hit me up with any Questions / Comments / Issues!

Pushing out a build that is basically identical, because I'm an idiot.

I didn't realize Unity Analytics was Activated, and for many, that's a privacy concern to have usage stats being beamed to some arbitrary server somewhere.

Since I don't use it, and wasn't even really aware of it until it was brought up by user Amylion on the Discussion board, this build will have it disabled!

I want to apologize to everyone for leaving it on, and I hope this lapse in responsibility and due-diligence towards making safe, secure software doesn't permanently dissuade you from use TurnSignal.

If it does, but you still think the software is useful, feel free to audit and compile your own version from the source code, found on my github.

Thank you for your time and patience!

Heya, Developer of TurnSignal here!

That last annoucment may have been a bit intense, but it seems the bug was not as large as I thought, and even still, I have yet to think of a better way that combats the roots of inaccurate tracking.

So, in the meantime, I'm reaching out to try and see what features, improvments, or changes you would like to see in TurnSignal!

Things like new settings, new ideas about what the pattern should be, or how it behaves, maybe something with steam cards achievments or other SteamWorks features,

Really, I just want to know how I can make the utility better for the people who use it!

So, with that said, feel free to comment here, or make a new thread in disscussions, but I would love to hear your feedback!

I can't garuntee I will use every request, but I will do my best to read them all, and respond to as many as I can!

I really want to thank everyone for their support, It's meant the world to me to see how much people seem to like TurnSignal, I had no idea it would be so well received!

Ack, I dreaded when this would happen;

I've gotten several reports the the new tracking system in version 2.3.4 can somewhat randomly, but reliably, goof up the ammount of turns you've made, making untangling innacurate, and that's no good for anybody.

As a quick fix, I will push out an update that includes a toggle for switching between the older method, and the newer one, ( and of course saves it ) until I've gotten the issue resolved,

Look for that workaround / fix update later today / early tomorrow morning!
(Unless I can replicate and fix the issue that fast)

As a faster solution, for those who want / need the original core function NOW,
I will push the previous version out as a beta build you can select from the Beta's tab under the apps properties in Steam,

I honestly feel terrible, for everyone, not just those who've experienced the bug, that I let an issue this big, that reduces useability at all, into what should be a trustable peice of software.

Thank you for your support, especially those who submit bugs for fixing!
The squeaky bug gets squashed!

TurnSignal has been updated to 2.3.4!
This time, actual improvements!

• Fixed Menu / Display Bugs!
  
• Hopefully, Massive improvement to Turn Tracking ~ !

I've decided to completely give up tracking the rotations via the absolute Y rotation, and have now switched over to tracking rotation based on angular velocity.

So far, it seems to be significantly more accurate then before, tracking turns even in the previously buggy task of looking up or down while turning!

Hope it works better for everyone.

As always, feel free to contact me for any Issues / Questions / Feedback you might have!