Changelog-3.0.0.86: Added Windows 8 Compatibility Fixed Sleep/Hibernate mode Bug (Experimental – Only tested on my laptop with Windows 7/8) – 3.0.0.64.
Filters Links Dates Event Period: (includes Hongsil's Secret Storehouse, Tower of Memory, Royal Raid, and Joy to the Realm Jackpot Events) December 5th-January 16th Holiday Treasure Trove: December 5th-December 26th Outfit Rotation: November 26th-December 14th Current Ladder Season: December 12th-February 6th Rules This is a summary of the rules for this sub. To find an in-depth version, please go to. Please stick with content related to Blade & Soul. Please use the search function before posting a question or request.
![Windows Windows](http://i.imgur.com/p0CtPFI.jpg)
Chances are someone has had your issue before. Criticism is allowed, but do so in a decent manner. We can't assist with technical issues. Contact NCSOFT for any tickets, support at.
Hi everyone, I am trying to run blade and soul on the 64 bit platform, but it never seems to work well. I am just wondering is there anyone who has got this solved?
Problem 1) I tried to launch the 64 bit through the game launcher. (It appears on Task Manager for a few seconds and just randomly quit itself) my solution to Problem 1: - I tried changing the compatibility setting for Client.exe (64 bit) to Window Vista, Window 7 and Window 8, and this allowed the game to be opened.
However, the game is capped at around 30FPS. I am suspecting that it is using only the Integrated Graphics Card, rather than my GeForce® GTX 970M. My solution by changing the compatibility doesn't really help, as the only reason I am trying the 64 bit client, is hoping to reduce the FPS spike, stuttering and etc. Some may wonder it must be my hardware problem, so here is my Spec: Intel Core i7-6700HQ CPU (up to 3.50 GHz) GeForce GTX970M 16.00GB RAM 3840x2160, 60 Hz Resolution Window 10 Installed -SOLUTION EDITED - Thanks to kaigame from BnS Dojo and Mightflash After numerous Research, I have found out a solution to my situation: pretty much the 64 bit Client runs very poorly with compatibility setting of Window Vista/Window 7/Window 8. However, there is a way to force 64 bit Client to launch with compatibility of WINXPSP3: Run Regedit by 'Ctrl + R' then type regedit and press Enter. Go to HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion AppCompatFlags Layers. If there is no 'Layers', create one.
2) Create a new string value, and name it as the full path of the Client.exe file. By default, that would be C: Program Files (x86) NCSOFT BnS bin64 Client.exe 3) Set the value of the string to ' WINXPSP3 HIGHDPIAWARE' Notice: 'WINXPSP3' works best for Windows 10 Pro 64bit and 'WIN7RTM' appears to work best for Windows 8/8.1 Then I also added in another string value as: C: Program Files (x86) NCSOFT BnS bin64 BnsCefSubProcess64.exe With a string value of ' RUNASADMIN' Some reported the 64 bit Client crashes after loading 58MB. If that is the case, gameguard is actually the process that is killing the 64 bit Client as CefSubProcess cannot be executed propertly.
In this case, only bypassing, fooling or disabling gameguard then using my method could help. However, this could well be against the ToS and therefore one must use it at one's own risks. I have pretty similar computer composition as you do. I also had the same problem, huge fps drops, freezing and everything. 32 bit client worked decent but it also had some fps spiking. I had insane fps drops when I tried to do MSP. I tried literally everything, from overclocking to NCSoft support (They were as useless as ever).
How I finally solved the issue: I formatted my computer and installed windows 7. No more fps drops, constant 120 fps with 64bit client. The issue is caused by a combination of things; your processor, drivers and windows 10 (directx12).
The game was made with an engine that used directx 9, which is pretty similar to directx11 and how it handles. Directx12 is better and it had backwards compilability but the game is so poorly optimized for mid to high end pcs it does not even matter. So if you want to play this game, buy windows 7 from internet (like 20-30 euros from kinguin). That worked for me, and I literally tried everything before switching windows. Thanks to kaigame from BnS Dojo and Mightflash After numerous Research, I have found out a solution to my situation: pretty much the 64 bit Client runs very poorly with compatibility setting of Window Vista/Window 7/Window 8. However, there is a way to force 64 bit Client to launch with compatibility of WINXPSP3: Run Regedit by 'Ctrl + R' then type regedit and press Enter.
Go to HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion AppCompatFlags Layers. If there is no 'Layers', create one. 2) Create a new string value, and name it as the full path of the Client.exe file. By default, that would be C: Program Files (x86) NCSOFT BnS bin64 Client.exe 3) Set the value of the string to ' WINXPSP3 HIGHDPIAWARE' Notice: 'WINXPSP3' works best for Windows 10 Pro 64bit and 'WIN7RTM' appears to work best for Windows 8/8.1 Then I also added in another string value as: C: Program Files (x86) NCSOFT BnS bin64 BnsCefSubProcess64.exe With a string value of ' RUNASADMIN'. Mode This is what happened to me before and even yesterday, so I tried my own method again.
The reason why the 64bit client.exe kills itself is because of the interference of gameguard. Basically, Gameguard must be disabled, or bypassed (or fooled).
I have got tools for that, but that it may be against the ToS, so I won't post it out. The 64bit kills itself (because of gameguard) after loading approximately 58MB or so, under the XINXPSP3 setting. So the ultimate solution to the 64bit is to find a way to bypass or fool the gameguard so that it does not interfere with the Client and kills the Client.exe.
There are many methods in fooling gameguard but it is very lengthy to explain. There are reddit posts on how to disabled gameguard and that would work with the WINXPSP3 setting. However, use it at your own risk as there is not definite, offical method fixing this right now.
![Bit Bit](http://i35.servimg.com/u/f35/19/52/77/01/screen26.png)
Sorry for not giving credit to you as I couldn't find your previous post earlier, I have already added back in. I had literally spent hours and hours, looking for a working solution, so the browser history is like full of URL on reddit posts, it was hard to me to identify which one was yours. Yeah I saw your posts and it helped a lot. Editing that particular part of the registry would not have any harmful effect to the operation system itself (as that string value can also be well replaced by simply right-clicking and changing the properties setting of a certain document), but we can't expect everyone to know what that part of the registry is doing. However, I have also modified other documents, in order for your method to work (I tried your method after I have modified different stuffs and the second time I tried it didn't work; However, I have already found a very stable way of launching it in 64 bit now - using your method + a bit of mine in fooling GG). Basically, Gameguard must be disabled, or bypassed (or fooled).
I have got tools for that, but that it may be against the ToS, so I didn't post it out. This is because the 64bit kills itself (because of gameguard) after loading approximately 58MB or so, under the XINXPSP3 setting. So the ultimate solution to the 64bit is to find a way to bypass or fool the gameguard so that it does not interfere with the Client and kills the Client.exe.
There are many methods in fooling gameguard but it is very lengthy to explain. There are reddit posts on how to disabled gameguard. However, there is not definite, official method fixing the 64 bit Client.
I can fully understand the situation. My head and my browser history were full of 'possible fixes for fps problems' but nothing helped at that time. I also did everything I could find from process hacker to Nvidia inspector and of course also BnSBuddy (or Ark). I suspect you have had the same thing patched to your client prior to this fix. What a shame that NCSoft cannot get their game to work for everyone and some people literally have to dig deep into Google and Reddit to find any clues on how to possibly fix something with a low chance of success:/ their official ticket response is always 'Do the File scan in the launcher' or 'reinstall the game', like 'did you even try to turn it off and on again?' :D.
Not sure if I'm posting this in the correct category, but here I go anyways: I have an old laptop (which is unfortunately my only computer) with a Mobile Intel 4500MHD iGPU. I've been looking for ways to improve performance, and I think I have pretty much done every trick in the book, but I'm still looking for more ways to improve performance. Anyways, I recently found out about Royal BNA drivers. Currently I'm using PHDGD Quebec 4.0 drivers, but Royal BNA does seem interesting.
Royal BNA seems to be from 2013/2014 and PHDGD is from 2016 (both of which is ofc newer than Intel's official ones). I'm wondering if I should stick with PHDGD, or is Royal BNA better? I have a 32-bit OS, so any modern game is 100% out of the question. Both of drivers give similar performance since all they do are simple registry tweaks to Intel's last released driver 2869 to make the dedicated graphics ram 128 MB instead of 64 plus change the name of the driver so all games that block such GPU (some do yes) would not recognize it and run. There are few things you should be aware of though: 1 - 32 bit windows only utilize 3 GBs of ram which is more bottle neck than having such a GPU where I suggest you do both a ram upgrade and windows (to 64 bit) to get much better performance than what you have already, the SODIMM Rams DDR3 PC3 0 are at their lowest prices right now, having 2 x 4 GBs sticks to run at dual bus speed might improve things dramatically for you.
2 - With any of the upper suggested drivers installed you can work a huge selection of the window 10 store games at surprisingly high frame rates including Asphalt & Modern Combat 5 as most store games are optimized for tablet performance which is not any better than the GMA GPU, but then you need to upgrade to windows 8/10 sadly to benefit from this.