It happened once or twice to me... try with alt+enter to go fullscreen/windowed mode and just experiment.. i honestly dont remember how i fixed this one
This is just a small update to fix minor issues related to the starter.
UPDATE R253
- Minor improvements/updates to close game, open game, run time calculations, and crash recovery
- Added a game client move/resize prior to the initial iteration of the character select Play button search
NEXT UP
- Bug hunting - correcting inadvertent session end time changes after a crash recovery
i'm even having trouble downloading the patches for this game in a virtual machine. anyone had that problem?
ok, fixed the red screen issue. i basically had to let it stay in that crazy high resolution it starts with and go into the game preferences and change the resolution of the game. in other words i did not hit alt+enter to resize it.
Last edited by UseTheForce; 10-04-2012 at 01:22 PM.
will there ever be a way to record missions? i love the ui/crew skills functionality of luckys but i keep reverting to untz for the sheer fact i can make more xp/creds per hour due to being able to get bonuses in..and the broken missions in luckys doesn't help either. untz's crew skills functionality is terrible tho. i haven't updated either for a while due to bugginess, maybe it's a little better now.
Having an issue with the crew skills. Bot doesn't recognize that all crew members are on missions already.
The crew window opens, cursor clicks in the crew window as if selecting treasure hunting then moves to where the missions window would be and continues moving as if it were scrolling through missions.
Luckys Spacebot v5.35 x86 (R254)
System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:4 GB, used:48 %
Desktop dimensions: 1920x1080(32bpp, 60Hz)
Desktop theme: Aero using NormalSize, NormalColor, 96dpi
SWTOR Client is running with 1024x766
SWTOR Window:0,0 Win size:1040x804
Color scheme: Aero
On Target Time=60
Missile Delay=333
Timer Skew =50
IMG Tolerance=99
HD Status=1
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=Aeten Defense
Win / Loss 0 / 0
Crew skills are next on the fix-it list. With luck, this will be addressed within the next few days. Thanks for the report!Having an issue with the crew skills. Bot doesn't recognize that all crew members are on missions already.
The crew window opens, cursor clicks in the crew window as if selecting treasure hunting then moves to where the missions window would be and continues moving as if it were scrolling through missions.
UPDATE 5.35 - R255
This update is recommended for all current users.
The following update fixes a number of major issues, and it might help with the bot crash issues which have been accompanying game client crashes over the past week.
The new revision can be found HERE on the current x86 trunk.
Changelog:
- Fix: Multiple game play sessions are once more working as intended
- Fix: Starting game play sessions with the game client closed will now work as intended; the launcher will not start until the next session is scheduled to begin
- Fix: Session times beginning with the hour "12" will no longer cause negative numbers to display in the minutes field
- Fix: Potential memory leak: This was an issue with the original code - missions started from the Main tab will no longer force a call to the start2() function from within the start2() function after the first mission is run; ContinueLoop is now used instead
- The session input entry field will now clear after each session is added
- The session mission will now be saved after the bot has closed
- If HD mode is on, after a restart, the "Remaining" time will not be updated until the ship has finished loading
NEXT UP
- More bug hunting
- Crew skill fixes
I have not been able to get this spacebot to work even once. Every time I start a mission it exits out to character select. Oddly enough version 5.31 works like a charm and without a hitch.
Any ideas on what I need to do to get this to work?
Luckys Spacebot v5.35 x86 (R255)
System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:4 GB, used:41 %
Desktop dimensions: 1366x768(32bpp, 60Hz)
Desktop theme: Aero using NormalSize, NormalColor, 96dpi
SWTOR Client is running with 1024x742
SWTOR Window:0,24 Win size:1040x780
Color scheme: Aero
On Target Time=50
Missile Delay=333
Timer Skew =
IMG Tolerance=125
HD Status=1
Timing override=4
Mission bonus=4
PSX OTT enabled=1
PSX DBG enabled=1
Last mission=Mugaar Ice Field
Win / Loss 0 / 0
Hi Bradoshado,
Your desktop needs a higher vertical resolution than 768 for the game client reach the necessary size to run without issue. The game has to run at 1024x766 (1040x804 including the window frame) or it simply won't find many of the buttons and mission targets. Also, missions run best with psx debug unchecked because this allows for autofire.
If your monitor won't go any higher, one solution would be to set the game up through VMWare Workstation, which allows for higher resolutions, using scroll bars as needed. Instructions for running SWToR/Lucky's on Workstation can be found on page 19 of this thread.
I have a question to you TMichael regarding Luckys..
How are you taking the screenshot of the credits for the newer builds? I'm fooling around with a "foolproof" way of getting back in to the game as SWTOR has the "crash-to-desktop-immediately-when-you-leave-the-computer-and-then-the-crash-recovery-wont-working" syndrome. Why i'm asking is because it would be nice (for me atleast) if the autoit script i'm making took a screenshot of my credits (with a timestamp).
anyone know what happened to the noob766's version of untzbot page, its no longer there...