Jump to content
  • Forum Statistics

    Total Topics
    Total Posts
  • Member Statistics

    Total Members
    Most Online
    Newest Member


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Teszty66

  1. Its a bot that auto generates posts based on the thread content I think, and then appends some ads. There is a lot of them in the forums.
  2. Yes, it is more designed as configure once and forget type thing. But it is not that cumbersome to do, basically you go to "Manage Service" menu, there you can keep easily restarting the service each time you edit the config. I have a low priority todo item that would add live reload of the config but I dont think it is worth the effort.
  3. That means asus has built in the controller into their motherboards, pretty cool. 99% of motherboards have a simple pwm controller that just reads cpu temperature and thats it. So having a separate box like thermaltake does means you can support more systems and dont have to worry about compatibility. Dont know about their official software but I wrote my own and it never failed once. You kinda confirmed that their software is bad, because windows does not cause the software to fail on its own. Not a fan of any os, each has their place.
  4. Not true, the controllers work just fine after resuming from sleep, they didnt add support for that in their software so there is no way for it to work. Because it allows you to customize the fans even more? What if you want your front fans to respond to the temperature of the gpu instead of the cpu? What if you want to quickly switch profiles from gaming to quiet. There is a lot you can do when you can fully control everything. You have separate loop for cpu and gpus, currently if you would render something using 100% of gpu and 0% of cpu your fans would not spin faster and they would reach high temperatures. Similarly if you are using 100% cpu and 0% gpu you have 8 fans that are making noise unnecessarily. I would rather suggest adding one pwm input like in the sync controller that would act as a fallback that would control the fans if there is no software controlling it present. And yes, the software is ####. Its not windows.
  5. Well, there is the same concept of boot/shutdown profiles in the github version, so you use the boot profile to change the defaults of the controller. You can have as many profiles as you want, but yeah the github version is more complex to setup. The documentation is still WIP and can be quite hard if you dont know what to do. You can create an issue here and I can help you setup the github version if you want, but the 1.7 should work just fine if you need simple profiles.
  6. The controller will use its default settings when there is no software controlling it. You can create a new profile and set its type to Boot and when you save it the controllers defaults will be set to those settings. But I think I made it so you cant stop the fans, you are forced to use manual speed so 20-100%. You can also set a Shutdown profile so when you are shutting down the system the fans will be set to a specific speed/rgb.
  7. You just need to make sure its not running, remember to also disable autostart. It might some day but its a lot of work for something you use only once on first setup and never again. The github version is made so it is heavily and easily extensible with custom effects/speed controllers/triggers/new devices, this makes it hard to design a gui. Also with right triggers you can make it very dynamic, like for example switch profiles when a program is launched, or program a custom discord trigger that changes rgb when you get a new message etc. You probably had the official software running and something broke. The gui version would need a complete rewrite for it to be further developed since it is written in a very limiting way, this is because I had less knowledge about the inner workings of TT controllers. So it is unlikely I will work on this version again, maybe someday I will add a gui for the github version. The only supported effects in gui version are those builtin the controller, so I cant add more unless I rewrite 90% of the app. But you can write custom effects in the github version, if you have any in mind I could add those.
  8. I think you downloaded the version from github. It does not have gui right now, and probably never will due to the highly increased complexity compared to the old version. The old version is attached to the first post and it still works, but its much simpler and has some limitations (always assumes 12 leds and only uses built in effects)
  9. Yes it can. The manual mode goes only from 20% to 100%, but you can set the off mode to stop the fans or use the pwm mode so they stop below a specific temperature. Fyi the fans cant spin at speeds 1-19%, so its either 0% or 20-100%.
  10. Interesting, then my only suggestion is to try the github version because you can set how much leds each device has.
  11. Everyone, and there is no fix because its how the software is written. There is no way to set PWM curves, but you can use this.
  12. Or they could make it a service so you would only need to elevate once to install the service. It even makes the fans work before you login. But no one seems to make software that way, I guess the money is in the hardware not in software. @Bioacid You can try this if you want.
  13. Please create a new issue here. Post the same info and translate to english if you can.
  14. @Eatsrootsnleaves Did you get to try the old or new app? I'm curious how it works with so many fans.
  15. ####, yeah this will be a good stress test for the app. I think it would be best to try the latest version. Please go here and follow the instructions, I'll then help you create a config to test your devices. The riing fans, PR22-D5 and Pacific RGB fittings should work fine. I know that Trio will not work correctly right now because of 3 zone settings, if you can help me get the data that I need I'll implement them. Dont know about the strimmer and the strips, if they are connected to the thermaltake controllers it should work.
  16. There is no problem with the controller, its that their software is #### and they just did not code support for sleep/wake. There is a command they send to the controller when the application starts, all they have to do is listen for sleep/wake events and reinitialize the controller/connection. This is what I do in my app and it works just fine with sleep and hibernate.
  17. LOL, well the pumps might be different but mine runs at 3000RPM on average load. And I think about 1500-1800 on idle. Also mine is setup differently, I have a dedicated pump port on my motherboard and Ive set the PWM curve to be always 100%, so it always gets full voltage, and then the RPM is controlled by the software/the pump itself based on temperature. Maybe it was not getting enough voltage on your previous BIOS settings and it was starting and stopping.
  18. Well, I dont know then. IMO it should not be doing that. Maybe the pump provides the wrong RPM values, or maybe HWMonitor is reading it wrong, or maybe the motherboard is providing the wrong value. There is a lot of stuff that could be wrong but it seems its just a problem with the values, if you dont feel the pump stopping and starting then the pump is fine. But for example my AIO spins the pump up and down depending on the load. If yours does not do that, your motherboard might not be controlling the pump correctly, or its by design and the pump always runs at static RPM. But that would be #### design from TT. You could read on how to connect AIO pump to your motherboard and how to setup PWM speed control in BIOS.
  19. Hmm how about service stopped and official software running? I dont think it should be doing that.
  20. That might just be the way the controller is programmed, since you cant pass to the controller how many leds a device has, so I think it also assumes 12 leds per device. Thats why I said to try with the full black, maybe it detects the black as limit for leds. Hmm that sounds like it does not set the speed then. Unfortunately the old app only sets the speed by percent. The RPM going to 0 and back might be a conflict with another software, at least this is what was happening to RPM of my fans when I had the service and the official app running, they were both writing to the controller and it was freaking out. If the fans also see this behavior check if the official software is running. Aida64 added support for TT fans some time ago and it also causes this issue. Ooh I see, so the pump is also connected to the PWM of the motherboard. I guess that means you can only configure rgb on the AIO and the pump is controlled by the motherboard speed controller. But that does not explain why it goes to 0 RPM. Does it also happen when you stop the service? Maybe you can control the speed but the TT controller and the motherboard controller are interfering with each other. Dont know if I will be making a GUI for the new one since its a lot more complex. And you should check github if you want updates about the new version, I wont be posting about it here. Yes they should work fine. Although they have 9 leds and the software assumes 12 leds so some rgb modes might behave weird.
  21. @Zeonymous Wow yea antivirus be like that sometimes. Glad you figured it out. Im also using PIN and never had to disable it, so I dont know whats up with that, probably also the av. You could try changing the install to custom user/LocalService depending on which one you use now. And about the AIO, if I understand correctly you are saying that the AIO has 6 leds but the fans have 12, so the rgb modes are not displaying correctly, right? Yes, that is the limitation of the old version of the software, because when I was writing it I thought only fans would be supported. Now I know that all TT RGB Plus devices use the same commands to control the speed/rgb, so while the rgb will work on all devices, it thinks all of them have 12 leds. Although I think you could try setting the last 6 led colors to full black (RGB 0,0,0), maybe this will trick the controller. Also please note that I have not tested any pumps, so I dont know if the command that is sent to the controller is the correct one. Try setting the speed to manual and changing it from 20% to 100% and see if it makes a difference in sound/vibration etc. There are 2 commands, one sets speed by percent and one that sets speed by RPM. The pumps might use the second one. The new version on github allows you to specify how many leds are on each connected device, and a lot more features. But it might be hard to configure right now because it does not have GUI.
  22. First release of the new app added on github if you dont want to compile yourself.
  23. They new one has no gui yet. I dont know if I will make one because I added a lot of features that will make gui very complex. But I will see. You can download the old one in the first post. It works fine and has gui, but the code got a little messy from features some people requested.
  24. Initial code for the new version posted on github if anyone wants to compile it.
  25. Yea try v1.7, it has no port detection that seems wonky on some setups. I will try disconnecting my pc from power and see if this will reproduce the issue. The new app also has no port detection, you configure each port manually by setting its name/led count/led rotation/led reverse and other stuff. Also at first the service will have no gui, only json file config.
  • Create New...