Earthsiege2 "CopyFromCDToHere.bat" wrong path #18
Comments
|
Ouch, what a mess. That batch file copies everything to the current working directory regardless of which directory the batch file is in. This was intentional for some reason which I forget at the moment (probably because I don't like overriding the current directory if I don't have to). Thus, somehow, you are running it from System32 (which is where cmd.exe resides). But, how? That is the question. I suspect this is the reason (you are likely running the batch file as Admin): Thus, you can either not run it as admin, or run it from the command line from the directory you want to copy to (which may be your only option if using Windows Vista). I should update the wiki to clarify the Admin issue. I will also consider changing the batch to always copy to the batch's location instead of current directory -- although, I kinda doubt I will. Regardless, the term "Here" is somewhat vague on that either way. Thank you for the report. |
|
Yes, that was it! Thank you very much. You might want to consider writing a note in the instructions for this too, because that was the first place I looked for a solution. |
|
Glad to hear we got the batch file worked out. Thank you for your help with hammering out the install instructions a bit better. As for the slowdown with ES1 and 2, I can't say I know. I haven't tested ES1 as Windows games are my current focus because DOSBox does a good job with DOS games. I assume you are running ES1 with DOSBox so the speed there would depend on your DOSBox settings. With ES2, one of the compatibility settings installed here switches the game from trying to use the GPU to the CPU only (or so it is said). But, since the game takes only 18% of my CPU, I would be surprised if any modern system couldn't handle the game's CPU demands. I haven't seen a memory leak with this game yet, which would be the usual cause of a slowdown over time. Thus, I'm guessing the real problem is that, as you said, they get slower the longer you play. Both of them? A DOSBox game and a Windows game? That would indicate something very fundamentally wrong with your system and I couldn't possibly guess what other than update your BIOS and all your drivers. |
|
I really don't know with my system sometimes, it only gets the most exotic and exclusive problems ever and rarely any of those "peasent problems" most other people get... |
|
In mysterious situations like yours, I typically learn a lot just by watching the Task Manager in Windows while I test the game. Click More Details to see the details, then click on the column headers to sort by CPU or Memory or Name or whatever I suspect the most. Sometimes I use more advanced tools but usually Task Manager is enough to understand most situations. |
|
Re the Razor, as you probably noticed in my joystick setup notes: "No comment on flying herc settings." Razor controls do work, but mapping them in a sensible way to every Windows controller was beyond the scope of my work. Probably because there were mapping limitations that prevented an obvious set of hints here. I don't recall if I ever succeeded in controlling the Razor with a dual-analog controller or just resorted to the keyboard or a flight stick or what. I'll think about looking at it with an XInput controller sometime to see if I can at least write a better hint for that standard. Your controller has two modes and it's anyone's guess which will work better for you: XInput or the older-but-more-flexible DirectInput. You often need the Logitech software and driver to take full advantage of controllers like these. |
|
Well, I actually meant I can't control the altitude with the keyboard... which is why it confuses me. But maybe I need to use the gamepad for that one... |
|
Okay, yeah, that is weird. I just tested with the keyboard and found the same issue. Apparently, setting the joystick controls also changes the keyboard controls... or something like that... and you can't change them back without a joystick connected. That's annoying. To get your default keyboard back, copy DATA\PREFS.CFG from the CD and overwrite the one on your HD. You can also just delete PREFS.CFG and it'll create a new one with all the features turned off. If your gamepad is causing issues like that you should try its other mode, and also make sure you are running the latest software and drivers for it. |
|
3 keys to go fast, none to not crash into enemies, lol. It works now though, thanks. |
|
From what you've said so far about slowdowns, it doesn't sound like an issue in the games, but an issue in Windows. Thus, it's more about fixing things to keep other things in Windows from interfering with the game, and not exactly about helping the game run better. It could be your USB drivers, your gamepad drivers, the Logitech software, or who knows what. That's why Task Manager is helpful in narrowing down the suspects. |
|
One last thing: got an error in luna mission 4 waypoint 3: "Assert: Line 69 in "objlist.cpp": ObjList: drawTable full". Do you have any idea about that one? |
|
I did a search and found this for you in the notes of this video: https://www.youtube.com/watch?v=PuhabfSSGHk&t=763s
This is the first I've heard of this error. I'll add it to the wiki and mark it for further investigation. I also plan to spend some more time with an Xbox controller in this game to see if I can write some better hints there. I spend most of my time making or fixing games and not necessarily playing them (and solitary games, especially, don't keep my attention well). I rely on others for complete testing (except, I do test my own games completely). I've tested ES2 pretty hard but haven't played it through. Thus, this is why I haven't seen this myself. I am surprised, however, no one has reported it before. Thanks, again, for taking the time to report this. |
|
Bummer, because it IS fun... which is why I asked for solutions because I was already at "Well, maybe I just fly to each waypoint and try to quit the mission then.", just to be sidetracked because those fuel tanks... they are just... too tempting to blow up in packs with the plasma cannon... and then the gun turrets annoy me and those red dots on the map distract me and and and etc pp... |
|
Yeah, total bummer. I suppose the best answer for now for others is to save the game, enjoy as much of the level as they can before it crashes, and then go back and just fly through it. |
|
There is some possibility DxWnd may be able to keep it from crashing, but that tool is a headache and I'm not up to digging into it right now. And, then there's the matter of getting to the Lunar sector... |
|
The wiki just got a pretty hefty update from all of this plus my latest joystick testing. Closing this now. Thanks again. If you find something else, just open another issue. |
The .bat seems to have issues copying the data to it's current location. It copied everything to System32 on my System.
The text was updated successfully, but these errors were encountered: