republicinator
-
Posts
34 -
Joined
Content Type
Forums
Blogs
Events
Articles
Downloads
Gallery
Posts posted by republicinator
-
-
Hello! I'm not sure if you found a guild yet, but possibly give Sokan Advanced Recon a look? We're a heavy RP/PvE guild that is always on the hunt for more members. Head on over to our site, sokangaming.com/sarhome for more information or just pm me!
-
I'm not familiar with what RP Imp guilds there are since I mostly play Pub side, but, Lords of Sokan may suite what you're looking for. sokangaming.com
-
Sokan Advanced Recon, or SAR, is always looking for new recruits. We are a heavy RP/PvE guild looking for people to join our ranks. SAR provides daily events, an HQ, FS, Ranks and Active Members. Interested in joining? Get in contact with my SAR toon, Korthus by either whispering or sending an in game mail and I'll get back to you when I can! Or head on over to our site at sokangaming.com/sarhome and click 'Oath of Enlistment' to submit an app for a recruiter to get in touch with you. Must be 17+ to join
-
It is against the ToS to put your link in a post. You can only have it in a Signature.
Forgot about that oops
. its gone now -
Any websites/apps that let you view SWTOR characters?
-
This err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0 made me wonder if you have any memory allocated in the settings. Check if you have any values in Configure > Display > Video memory size.
Did you recently have any updates to your drivers? Does Mac use mesa drivers?
I'm not really gonna bother with wine or PoM anymore since I'm using a "trial" version of windows running boot camp. Runs WAY smoother and doesn't crash or anything.
-
And when I run it through wine staging now it says theres an issue with sector_fix. I can hit play and it will go to the loading screen but ill just see the loading screen and it will appear as its in windowed mode and the rest of the screen is black.Do you use PlayOnMac? There is a debug option to run the game. Maybe it would tell what's wrong. I had loading screens hanging a couple of times, but force shutting down the game and restarting worked. It were some "hiccups" only.If you don't use POM, does Mac have a console, similar to Linux, that you could run it through a command? It should list errors too.
-
Do you use PlayOnMac? There is a debug option to run the game. Maybe it would tell what's wrong. I had loading screens hanging a couple of times, but force shutting down the game and restarting worked. It were some "hiccups" only.
If you don't use POM, does Mac have a console, similar to Linux, that you could run it through a command? It should list errors too.
Here is my debug file for POM. On POM it doesn't even initialize. It just sits at the launcher like its downloading a patch and nothing happens.
[08/11/17 04:44:33] - Running wine-2.14 start /unix swtor_fix.exe (Working directory : /Users/stephenwessels/Library/PlayOnMac/wineprefix/SWTOR/drive_c/Program Files/Electronic Arts/BioWare/Star Wars [08/11/17 04:44:33] - Running wine-2.14 launcher.exe /unix swtor_fix.exe (Working directory : /Users/stephenwessels/Library/PlayOnMac/wineprefix/SWTOR/drive_c/Program Files/Electronic Arts/BioWare/Stafixme:file:SetDefaultDllDirectories (800): stub
fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not supported in this platform
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0x33cbbc, overlapped 0xeeb310): stub
fixme:winsock:WSALookupServiceBeginW (0x33cc68 0x00000ff0 0x33cca4) Stub!
[0811/044433:ERROR:network_change_notifier_win.cc(111)] WSALookupServiceBegin failed with: 8
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:win:EnumDisplayDevicesW ((null),0,0x336818,0x00000000), stub!
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:win:EnumDisplayDevicesW ((null),0,0x334408,0x00000000), stub!
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:win:EnumDisplayDevicesW ((null),0,0x3347d8,0x00000000), stub!
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:win:EnumDisplayDevicesW ((null),0,0x336808,0x00000000), stub!
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:win:EnumDisplayDevicesW ((null),0,0x336808,0x00000000), stub!
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:win:EnumDisplayDevicesW ((null),0,0x336848,0x00000000), stub!
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:win:EnumDisplayDevicesW ((null),0,0x3367e8,0x00000000), stub!
err:d3d:wined3d_dll_init VideoMemorySize is 0 but must be >0
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:win:EnumDisplayDevicesW ((null),0,0x55dae68,0x00000000), stub!
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:win:EnumDisplayDevicesW ((null),0,0x55d9c58,0x00000000), stub!
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:winsock:WSAIoctl ignoring keepalive interval
fixme:win:EnumDisplayDevicesW ((null),0,0x55d9928,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
err:avicap:query_video_device Video 4 Linux support not enabled
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb46-f175-11d1-a392-00e0291f3959} not found
-
Cool! I heard it's fixed for 2.14-staging...
But it doesn't show in my POL for some reason yet. I can use the fix until the does, so no biggie.
Glad you -- and others -- can play again!
Hey, played for a bit today in like 2 weeks. Logged off to go do some things, shut down my MacBook Pro and when I came back to play again, It just stops at the loading screen directly after I hit play. Any clue on how to fix this? I'm using wine staging.
-
Yes and October is 7 weeks away
yeah ik. I only said October since there isn't a specific day in October that it will stop reading the certs. So that is still currently unknown.
-
A very very temp fix , in 6 - 8 weeks it stops working again ... and only fix will be not to use XP/Vista based OS / VMs
its supposed to last until October of this year.
-
I find it pretty hard to believe that there's thousands of people who still use xp or vista
Yeah, well it might not of been thousands but still a decent chunk of the player base. Thats also probably due to money or some other reasons why people haven't upgraded to bought a new PC entirely
-
Its good to see BW finally get down to business and fix the issue that so many people were having. But the only negative thing that can be taken from this is that thousands of players had to report the same issue. If this is what takes BW to do something like this then just imagine a major bug that is only happening to a few people that can't be fixed in-game...But still. Props to BW for addressing this issue. Well, only a temp fix though. Unless you use wine-staging.
-
My computer is having the exact same issue and i have been unable to play for 8 days due to it meaning that 8 days of subscription has been lost i haven't found any useful info on how to fix it.
if the issue is still happening then download wine staging the latest version. It now uses windows 7 by default so you should be good. If you use playonmac download the utility from the dev tracker thread and place that in your directory for SWTOR. then run it and you should be back to playing.
-
No worries Whenever you have time to fiddle with it.
Never mind with the playonmac issue. Ran the launcher utility for XP and Vista and its now working there to.
-
No worries Whenever you have time to fiddle with it.
Wine finally updated their launcher config to use windows 7. So I should be good for now until Microsoft discontinue that OS.
-
No worries Whenever you have time to fiddle with it.
Hey um, my swtor somehow fixed itself. I downloaded wine staging 2.14 and ran launcher.exe through that and it's working now. Still doesn't with playonmac though.
-
Can you please paste the content of your launcher.settings file?
Sorry about taking so long to post my launcher.settings. Things have been getting very busy around here especially with college starting soon. Hoping to post it ASAP
-
If you still have the cert error popping, it means you did not revert to the previous launcher version.
Let's try step by step:
1. Download the old version http://cdn-patch.swtor.com/patch/LauncherRepairUtilityP1.8.2.exe
2. Save/copy the old version 1.8.2 to the game folder where the launcher.exe is.
3. Rename /patch and /bitraider to /11patch and /11bitraider (you can delete them later)
4. Save a copy of your launcher.settings file to your Documents folder
5. Edit copy of your launcher.settings in your Documents file by adding
, "skip_self_patch": true
as the second line of the file
6. Run LauncherRepairUtilityP1.8.2.exe file. It should extract files, then close itself.
7. Copy launcher.settings from Documents back to the game folder. Overwrite the file in the game folder.
8. Try to run the game.
Any change?
it keeps adding in the files and when I run the 1.8.2 utility it keeps opening the NEW launcher.
-
If you still have the cert error popping, it means you did not revert to the previous launcher version.
Let's try step by step:
1. Download the old version http://cdn-patch.swtor.com/patch/LauncherRepairUtilityP1.8.2.exe
2. Save/copy the old version 1.8.2 to the game folder where the launcher.exe is.
3. Rename /patch and /bitraider to /11patch and /11bitraider (you can delete them later)
4. Save a copy of your launcher.settings file to your Documents folder
5. Edit copy of your launcher.settings in your Documents file by adding
, "skip_self_patch": true
as the second line of the file
6. Run LauncherRepairUtilityP1.8.2.exe file. It should extract files, then close itself.
7. Copy launcher.settings from Documents back to the game folder. Overwrite the file in the game folder.
8. Try to run the game.
Any change?
every time I try to run the game it just creates a new patch and bit raider folders. And when I open the directory of where my SWTOR files are those files aren't there. I have to run the launcher utility to get those files.
-
Your top post doesn't even mention you are playing on an unsupported OS. You shouldn't make player force you to cough up relevant details like that.
The devs need to fix it for Windows XP. When that happens, it will *probably* be fixed for Linux and Mac at the same time. Alternatively, you can build Wine yourself from source, and incorporate the patch that a SWTOR user made that adds the new certificate type.
But really, lets get the workaround going. If it reverted, I suspect you did not remove or rename the /patch and /bitraider subdirectories. That's just a guess: you may have failed to save launcher.settings or accidentally brought in a new one. In the other thread, someone had a copy named launcher.settings.settings that he was modifying (that his Windows box displays as "launcher.settings", because Windows often cuts off file extensions because Windows is awful).
Basically, walk through what you did and maybe the community can help. PoM, PoL... all the Wine based solutions, all of them are not supported by Bioware officially. I'm sure they'll help when they can though. My hope is that whatever they do for Windows XP will work for us though. Also I think you should get the workaround going, because once the fix is live you'll want to remove the
, "skip_self_patch": true
line from launcher.settings and have it suck down a correct one (whenever one exists). But if you are suffering from the bug, it just sits there and spins a CPU up and leaves it spinning- it isn't doing anything useful, such as grabbing a new patch. You'd probably need to end up at least partially reinstalling if you don't have the workaround working.
Whenever I try to get the workaround working I just get the same error. I do everything (at least I think) correctly and it still comes up with the certificate error. If you have or know how to get the workaround working is there any pointers/tips you could give me?
-
I'm not using a windows OS. I'm using a MacOS (playonmac) which I can't get the reddit workaround to work at all. It was working fine a few nights ago but now my sub time is just wasting away because of this. My playonmac uses windows XP but I'm not sure how to change it.I am not sure this is fixableWhat OS are you using ? from what I can gather XP and Vista appear not be getting root certificate updates anymore due to being unsupported OS by Microsoft
The certificates all have expiry dates and the one that was used by the launcher expires in October so they renewed it.
There is a temp workaround to revert to the old launcher however this will only work until October as once that certificate expires it will stop working , this workaround can be found at this Link
I am using Win 10 and have had no issue with the launcher update for example
-
Well, I don't know if any devs or anyone associated with the dev team will see this but its worth a shot. Will there be a hot fix for this certificate authentication issue soon? or will it be a while until this is properly addressed. This is causing me to have my sub time waste away because a "launcher update" caused the certificates to completely disappear. This REALLY, REALLY needs to get fixed soon devs, GET ON THIS PLEASE!
-
First of all, i wasnt blaming u i was blaming Bioware. What, do u work for them....thought you was just a helping person of the community? Second thing. What you said wasnt any thing that could break my game. You suggested to see if the launcher after disappearing, if it was running in task manager and like yesterday it was. Again what you suggested did no harm, it was good advice and it was appreciated. I just happen to, do that already, but you did not no that.
3rd, i wasnt being an A-- ---e to you and was just pointing out, Not maybe in so many words but, pointing out it was their patch that broke it so, 'BW, You Broke it, you fix it'. It had nothing to do with you dude. If you thought that then sorry, that was the furthest thing from my mind. Actually i was being more halfheartedly joking around. But i keep forgetting, no one can see my cheesy joking around smile through my text. This is why i hate texting of any kind no one can tell when your joking.
Oh well, Bioware fix it, dont fix it, i am bout to quit any way, cant progress on Iokath any way, cant get any help there neither. I just paid for another month yesterday, so i guess if it doesnt get fix by next month b4 payment is debited out. Then i am done..
Take Care & Please Be well.......
Ah, thought you missed a letter on BW and meant to say BTW. I'll take my L here. Hopefully your game gets fixed
. its gone now
Whenever you have time to fiddle with it.
Looking for some sort of Guild, ERP? RP?
in Star Forge
Posted