Jump to content
Corsair Community

Link Development Status Update


COOL GUY

Recommended Posts

  • Replies 143
  • Created
  • Last Reply
Really already I made the reservation windows 10, day 29 July is coming, the corsair will release an update? fixes and support for new windows

 

LOL don't get your hopes up. They haven't been able to figure out 8.1 yet, so W10 may be not happen for a while. OTOH, maybe they decided to just stop messing with the useless 8.1 version and concentrate all their efforts on W10, so they will finally have a working version, just not backwards-compatible... wouldn't that be something? It's fun to speculate like this, without any guidance or information from the company.

Link to comment
Share on other sites

LOL don't get your hopes up. They haven't been able to figure out 8.1 yet, so W10 may be not happen for a while. OTOH, maybe they decided to just stop messing with the useless 8.1 version and concentrate all their efforts on W10, so they will finally have a working version, just not backwards-compatible... wouldn't that be something? It's fun to speculate like this, without any guidance or information from the company.

 

 

LOL:laughing: the truth has been spoken sadly enough, but im hopefull.

if you can set it up just once its all fine you dont need to look at the crapfest ''software'' if you dont want to. :bigeyes:

im also hoping they would lower the 40% limit to 35% or even 30% and enable a 0RPM setting.

 

My previous fancontroller allowed me to run my fans at 25% RPM

and turn fans on and off as i pleased.

 

Atm some of my fans are blowing against a cover in my oepsair obsidian 500d for no real reason. (the cover will only come off during summer)

 

Would be awesome if i could set the commander up to only activate certain fans when they are needed like when the intake temps are arround 32 degrees celsius in dat summers :roll:

Link to comment
Share on other sites

  • 2 weeks later...

I would also like a 0 RPM setting to disable a select fan, I have a fan on the bottom of my case sucking air out (for dust control ), so when gaming and etc it would be nice to shut this fan off so colder air from the front fans gets to the GPU instead of getting sucked out the bottom, same thing with the top fan and rear fan.

 

 

Anyways to disable a fan would be great, if you don't like the feature keep your fans at 40% simple it won't effect anyone except those who want it, also my motherboard allows 0% on pwm so its not uncommon.

 

Throw a little disclaimer in saying don't use 0 RPM on rad fans then add a little fall-over protection ie if it detects a rapid coolant increase re-enable all fans as a safety measure, or do something like afterburner did where you have to manually edit an ini to enable overvolting a videocard.

Link to comment
Share on other sites

  • 3 weeks later...

I don't understand the Corsair software developers why not release betas and alphas openly or invite so the community can test and help discover bugs this way we can make Corsair product better all around not just hardware wise but also Software, lets face it the hardware is not as useful without the software....

 

Instead of just saying were done! we tested it with 5 coolers and 2 computers and 3 OS inside..

They must either be outsourced developers, not paid much, or just sloppy coders

 

 

really they should also release the API so other programs can control the hardware - I think it would draw more people to use Corsair products.

Link to comment
Share on other sites

This might explain "Copyright" infringement of software/hardware data being publicized?

Corsair Products - Featuring Asetek Technology:

 

Hydro Series™ H100i GTX Extreme Performance Liquid CPU Cooler

Hydro Series™ H110i GTX 280mm Extreme Performance Liquid CPU Cooler

Hydro Series™ H80i GT High Performance Liquid CPU Cooler

Hydro Series™ H110 - 280mm High Performance Liquid CPU Cooler

Hydro Series™ H105 240mm Extreme Performance Liquid CPU Cooler

Hydro Series™ H75 Liquid CPU Cooler

Hydro Series™ H55 - Quiet CPU Cooler

Link to comment
Share on other sites

I don't understand the Corsair software developers why not release betas and alphas openly or invite so the community can test and help discover bugs this way we can make Corsair product better all around not just hardware wise but also Software, lets face it the hardware is not as useful without the software....

 

Instead of just saying were done! we tested it with 5 coolers and 2 computers and 3 OS inside..

They must either be outsourced developers, not paid much, or just sloppy coders

 

 

really they should also release the API so other programs can control the hardware - I think it would draw more people to use Corsair products.

 

I need another computer,can I have yours?;):

Link to comment
Share on other sites

  • 2 weeks later...
Yeah.... v3.1.5667 and no "release notes! I wonder why! Dl'd it onto W10 b10240, has not crashed yet good news, but display ikons shows no info,bad news. only right click tray ikon to read pump and temp info oh well another fine mess.
Link to comment
Share on other sites

Yeah.... v3.1.5667 and no "release notes! I wonder why! Dl'd it onto W10 b10240, has not crashed yet good news, but display ikons shows no info,bad news. only right click tray ikon to read pump and temp info oh well another fine mess.

 

Even worse for me, followed the usual uninstall procedure, installed the new version and now Link won't open. Yay Corsair, because I really didn't want to control any of my fans or LEDS. Thanks a bunch.

Link to comment
Share on other sites

I suspect that Corsair had to release v3.1.5667 before they had planned to support the H110iGTX as the hardware was being shipped and v3.1.5570 does not support it. See http://forum.corsair.com/v3/showthread.php?p=790088.

 

5570 is just to support H110I GTX. That is why it was only put up on the product page for that product and all other product pages still have 5570 listed for support. Yes, on the main downloads page it is available, but if you dont have a H110i GTX it is not worth updating at this time.

Link to comment
Share on other sites

5570 is just to support H110I GTX. That is why it was only put up on the product page for that product and all other product pages still have 5570 listed for support. Yes, on the main downloads page it is available, but if you dont have a H110i GTX it is not worth updating at this time.

 

 

This should have been in the release notes, but there aren't any!

 

I think read some posts saying that it also fixed the H100iGTX custom curve.

 

As I pointed out in http://forum.corsair.com/forums/showthread.php?p=790485 the locking seems to be fixed, so 5667 is far better than 5570.

Link to comment
Share on other sites

  • 1 month later...
  • 4 weeks later...
God you would think after all this time they would get this software right. I love Corsair hardware products, I think they are some of the best yet the software to support them lags. Come on, if releasing beta builds or a SDK to the community will help sort out the bugs in it then lets have it. It may be what is needed to get it right.
Link to comment
Share on other sites

Have you fixed, or are you going to fix the registry bug that causes Corsair Link to act all schizo and lose it's memory, even though the profiles are still in the menus, and where it creates new devices for one reason or another, leaving the previous ones both non-functional, and zeroed?

 

I have been deleting my Corsair Link registry tree, and profile directory, and manually reentering by hand all of my profiles since I first reported this in the Cooling thread earlier this year.

 

I have been gradually isolating the problem since I bought my H100i GTX back in April, over the 20 or 30 times I have had to redo my profiles. Today, I finally think I isolated the cause by finding a fix that did not actually require deleting my profiles, and that was to simply delete ONLY the "Devices" tree under the Corsair Link tree in HKEY_Current_User/Software/CorsairLink/Devices, leaving the CorsairLink tree itself untouched. When I did that, everything came up nice, and all of my profiles actually worked.

 

I was about to post this in the forum here, when I noticed a new release, so I installed that, and am hoping I don't have to deal with this ever again.

 

Thje problem is definitely how you write out the devices into the registry.

Link to comment
Share on other sites

The problem is definitely how you write out the devices into the registry.

 

Firstly I suspect I am wasting my time trying to tell Corsair how to fix the profiles, but it's worth a shot given I have implemented a regime that actually works in SIV.

 

I think you are on the right lines, but feel the root cause is what rather than how. I expect the issue is in the design of the profiles rather than the implementation. All the CL devices are basically USB bridges which have up to 8 channels. On my system I have 10 bridges as below.

 

attachment.php?attachmentid=22867&stc=1&d=1442914207

 

The Bridge Device PnP ID is created by Windows when the device is installed, it is also unique and never changes. I feel the profile design needs to use this to identify the device which is what I do in SIV.

 

The basic concept is to map the Bridge Device PnP ID string to what I call the BID index which never changes. The rest of the profile information uses the BID + Channel Number. This regime has "just worked" since I originally implemented it. The same profile information is also used by new versions of SIV as I feed needing to recreate the profiles for every new release is inacceptable.

 

SIV can even deal with a Bridge Device PnP ID changing if you move the CL device to a different USB port as SIV will automatically update the above mapping table to map the new Bridge Device PnP ID to the original BID.

 

I suspect this will not get fixed in CL3 and hope that in CL4 the design of the profiles is improved.

2074084892_LinkExport.thumb.png.02c9bb9adbc9b8e17afd4356b161c174.png

Link to comment
Share on other sites

Does Corsair outsource their development team?

How could they get this so wrong?

Really If my developers were this bad I wood fire the all.

 

They need to think about either giving the sw out and make it open source or contract the design and development out to competent people.

Link to comment
Share on other sites

Does Corsair outsource their development team?

 

CL2 was developed by CoolIT and CL4 is being done by the same company as did/do CUE (http://forum.corsair.com/forums/showthread.php?p=793290), but I don't know about CL3. Neither do I know what will happen with CL4 once the development is complete. I have tried to find out and thus far failed. I don't even know who the CL Product Manager is and tend to feel Corsair Dustin would do a better job ;):.

 

I feel that CL will not be as good as it could be unless the CL developers get involved in this forum.

Link to comment
Share on other sites

My point is that they need a good/great architect to design the sw specs and should not have to rely on a forum.

 

Yes, the developers need to get the design right which should not need input from the forum, however the developers also need to work directly with users to resolve issues that they don't see on their test systems.

Link to comment
Share on other sites

  • 2 weeks later...
My point is that they need a good/great architect to design the sw specs and should not have to rely on a forum.

 

Actually I think Corsair has to consider Forum issues and comments in order to develop a fully working product.,Theirs so many different user builds that everything cant be tested in a controlled situation .

Its easy to design for a few but totally different when designed for any situation and build.

Link to comment
Share on other sites

  • 1 month later...

It's been 9 months since Cool Guy said Corsair was fixing among other things, the need for users to hack the registry, and would provide firmware updates for the H80i and H100i to address USB connectivity and RGB LED color profile issues.

 

So I downloaded the latest, and installed in my Win10 system. Pretty much not expecting much. First step after install and reboot was me having to update the registry manually. I still don't get why Corsair doesn't at least write a guide and tell customers they'll likely have to do so. Then I checked to see if there was a fix for the LED's set to zero issue on my H100i. NADA!!!

 

At least I can count on some things in life... Corsair is keeping their past track record of over-promising and under-delivering!

 

My best solution for Link, is to uninstall the software, unplug the fan cables, and control them via ASUS QFan on my motherboard.

Link to comment
Share on other sites

I figured out that inorder for my corsair link to detect the pump, i had to unplug the pumps power for a few seconds then plug ti back in. then the window for the firmware popped up. i said it must go ahead with the update and nothing happened. i since tried it again and now when i unplug the pump and plug it back in i only get this message.

 

"Corsair link has discovered new devices which require a reboot to finalize initialization. Click ok to reboot now or cancel if you would like to reboot later".

 

so i reboot and it pops up again when i open corsair link.

i reboot again. then the message doesnt popup.

 

if i go into my registry and edit the "AllowIdleIrpInD3" value to 1. then the same window pops up again asking to finalize initialisation and reboot......so frustrating.

 

also, when i plug the 3 pin (single cable) pump speed sensor into the motherboard cpu fan plug, it reads between 450-470rpm. i thought this thing was supposed to run 2000rpm.

Link to comment
Share on other sites

Just have installed the newest version on a Pegatron m/b with the original H80

H80 is out of diapers and turning 3 1/2 next month

working good for me

Im just a lucky sob batting 5 out of 5

fingers xrossed...

 

Well everyone, here's the long term solution everyone has been waiting for: just go ahead and emulate those hardware specs to guarantee a stable environment where Link can work as expected!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...