Quote:
Originally Posted by y2krazy
CrewBot will not work. Opens the Crew Skill (e.g., Scavenging) fine, selects the level fine, but when it goes to select a mission, it does not click on anything and instead of trying to click on Send Companion, the pointer goes to the location of the upper-right corner of the minimap. Resize issue?
I removed 4.1 to try 4.1x and when 4.1x had this problem, I tried a reboot. After the reboot, the problem still occurs, so I tried 4.1 again (since I used it previously and it worked fine) and now 4.1 has the same problem.
Thoughts?
EDIT: I neglected to change my settings to 800x600 previously. After I changed it to 800x600, when the bot starts, it resizes the window to SMALLER THAN 800x600, causing the pointer position to be off. How can I fix this? Thanks.
|
honestly, changing to 800x600 in the settings doesnt really do anything (it was an oversight on my part), as the bot resizes it to some 'smaller window' anyway
anyway, for default computer configurations, aero/classic modes will work fine, but for those who 'change settings', then you will need to use the debugger - watch video #1 for details
OR, do you mean, everything is fine (as in the bot plays space missions fine) but the crewbot simply does not work?
try checking your diplomacy settings - if you pick dark/light while NOT having diplomacy selected, it would do that
also, the crewbot should attempt to move to the 'cost' (in green) text and right click it
--
i will probably release 4.2, probably sometime after maint (again) as a quick update for 'debugging' purposes
it will STILL not include the crew sniping/multiple missions function, but will provide two things for debugging purposes:
4.2 proposed changes (or maybe 4.1x2)
- 'combat log', shows when missions start, wins/losses with timestamp, etc
- 'take screenshot when timer goes off' option
this is purely for debugging purposes and those who find the bot working fine might not want to change to this version as its just for testing purposes
oh, and
- fixed crewbot 'missing' on some characters (1->2, 2->3, etc)
i have noticed recently that some missions have 'weird' sync issues now, like 44clouds triggering IMMEDIATELY after loading screen (solved via changing the event sync file) and also 40drexel having two possible event sync positions (around 2 seconds apart from each other, so its a half-half chance of getting the wrong one - solved once again via changing the event sync file), so yeah, this is for those issues
i have a feeling its to do with this 'very low' setting being introduced, as even though you DONT use 'very low', 'low' still has had some minor changes - enough to break some sync files