|
|||||||
| Development Feedback & Discussion Feedback on the latest Beta drivers and future developments from Bigfoot Networks. We're always looking to hear back from those willing to test. |
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#61 | |
|
Community Manager
Killer Performance
Join Date: Jul 2009
Location: Austin, Texas
Posts: 505
|
Quote:
... And yes, we're fixing the site issues too. Ugh... |
|
|
|
|
|
|
#62 | |
|
Lagged
Join Date: Mar 2009
Posts: 23
|
Quote:
And the next time the site goes down I'll uncheck that to see if it works. .NVM Arrakiv : Answered it, its a bug. makes sense . |
|
|
|
|
|
|
#63 |
|
High Ping
Join Date: Nov 2009
Posts: 59
|
well not sure yet is the proplem on killer k-1 or something else, but i seem to get windows live messenger has stopped working everytime now when my computer is on and it isint on sleep either only not in use some hours. i have been sending the error report files to microsoft too and might post here when next time comes... this is just some random atm dont even know how long it has been AFK mode my computer i mean or is it just my windows 7 64-bit. Allso seems to get some times bluescreens when still playing dragon age origins on steam, happend 2 times only atm and they was some steam updates and game update/xpansion dlc update might have been that.
|
|
|
|
|
|
#64 |
|
Hitching
Join Date: May 2008
Posts: 37
|
Steam servers still not showing in Win 7 64 bit, sigh.
|
|
|
|
|
|
#65 |
|
High Ping
Join Date: Nov 2009
Posts: 59
|
well i have all steam server list and others showing nicly and now finally FNA firewall identivys Steam.exe allso but still huge issues ingame normal motherbeard network card ping on 1 server 55/latency about 40 plugged cable on killer card game first ping on same server 105-85 latency 80/90. but i know this is only beta so was hoping to get soon new drivers to test meyby new beta before official release.
|
|
|
|
|
|
#66 |
|
Lagged
Join Date: Apr 2007
Posts: 23
|
ok i've installed my killernic again using this beta driver (win7 64bit) installation worked fine, no problems here are the games i tested Call of Duty 6 Aliens vs Predator Demo Battlefield Bad Company 2 Demo Star Trek Online CS:S Mechwarrior Living Legends (awesome Mechwarrior Mod for Crysis) all are working without problems
|
|
|
|
|
|
#67 |
|
Hitching
Join Date: May 2008
Posts: 37
|
Maybe I should reinstall them again but on a fresh install of Win 7 64 bit the same problem persisted.
|
|
|
|
|
|
#68 |
|
High Ping
Join Date: Aug 2007
Posts: 53
|
Just also wanted to add...KIllertray never wants to remain visible. To be able to access it i constantly have to go to /start/programs/Killertray and manually start it anytime i want to change the mode its in.
|
|
|
|
|
|
#69 |
|
High Ping
Join Date: Jul 2009
Posts: 58
|
I dont know what, if anything, has changed between the beta and final version. But I installed the final release on my K1 in Win7 x64. The previous release drivers 4.1.0.37 beta worked without fault in everything. I did a total purge of those before installing the new final drivers. Problem is Modern Warfare 2 refuses to connect to IWNET while in Game Mode. It only works in App Compat Mode. That is the only issue I have seen. Unfortunately, this game is huge! ! How can a bug like this make it past testing, especially when it worked fine with the previous driver? This is the game of the moment folks!! I need my UDP offloading!!!!!!!!!! Here is my config: LLR-64 (Version=4.1.0.37) Configuration request KillerNIC K1 LLR Mode is currently set to GAME Mode LLR Version Number = 4.1.0.14 Proxy Version Number = 4.1.0.15 Firmware Version Number = 4.1.0.10 Card SubSystemID = 0x201 (indicates a K1) Number of Raw NIC SGLs = 1 Number of LLR SGLs = 1 Current LLR Ping Control= 0 Current LED CONTROL = Blinking LLR Game Priority = Boosted Boot Partition = Side B Boot Status Value = 0 Boot Running Status = KillerNic Boot Successful Boot Strap Version = 0x000003e8 KillerNIC Secondary IP Address=192.168.254.2 Mask=255.255.0.0 KillerNIC Tx Poll Timer Setting = 1000us KillerNIC Rx Poll Timer Setting = 1000us KillerNIC Firmware IP_TABLES is NOT Loaded KillerNIC K1 FNA support= Enabled LinkSpeed = 100Mps Mode=Full Duplex <==SetUdpConfig Winsock 32-bit Catalog: ======================= 1017 - BfLLR over [MSAFD Tcpip [TCP/IP]] 1018 - BfLLR over [MSAFD Tcpip [UDP/IP]] 1019 - BfLLR over [MSAFD Tcpip [TCP/IPv6]] 1020 - BfLLR over [MSAFD Tcpip [UDP/IPv6]] 1001 - MSAFD Tcpip [TCP/IP] 1002 - MSAFD Tcpip [UDP/IP] 1003 - MSAFD Tcpip [RAW/IP] 1004 - MSAFD Tcpip [TCP/IPv6] 1005 - MSAFD Tcpip [UDP/IPv6] 1006 - MSAFD Tcpip [RAW/IPv6] 1016 - BfLLR Winsock 64-bit Catalog: ======================= 1017 - BfLLR over [MSAFD Tcpip [TCP/IP]] 1018 - BfLLR over [MSAFD Tcpip [UDP/IP]] 1019 - BfLLR over [MSAFD Tcpip [TCP/IPv6]] 1020 - BfLLR over [MSAFD Tcpip [UDP/IPv6]] 1001 - MSAFD Tcpip [TCP/IP] 1002 - MSAFD Tcpip [UDP/IP] 1003 - MSAFD Tcpip [RAW/IP] 1004 - MSAFD Tcpip [TCP/IPv6] 1005 - MSAFD Tcpip [UDP/IPv6] 1006 - MSAFD Tcpip [RAW/IPv6] 1016 - BfLLR Killer Suite Version: 4.1.0.144 |
|
|
|
|
|
#70 | |
|
Fragged
Join Date: Jan 2010
Posts: 3
|
Quote:
i occasionally have the same issues with MW2 refusing to connect to IWNET. i believe it only happens after reboot, when i directly go into steam and launch the game. quitting the game, and fiddling around with the modes of the killer (changing to app mode and back to game mode) usually fixes the issue for me. i thought initially that it had to do with my firewall settings. but when i got so frustrated with the BSODs the killer kept giving me that i uninstalled it and returned to my onboard LAN for a while, the error was gone entirely. |
|
|
|
|