Hard Light Productions Forums
Hosted Projects - Non-FreeSpace => StarShatter Open Source Project => Topic started by: The E on June 03, 2012, 03:41:04 am
-
IfWhen you come across a bug, here's what you do to get it noticed:
1. Post about it. Either here, or on the Google Code bugtracker (http://code.google.com/p/starshatter-open/issues/list).
2. To give developers as much information as possible, please describe the steps needed to reproduce the bug, and try to reproduce it using the provided Debug build (Starshatter_D.exe). This build will generate two log files in your Starshatter directory, called errlog.txt and memdbg.txt. Please include both in your bug report.
-
The magic2 file included with this build seems to have trouble rendering texturs on the 3d models. When I loaded a .mag file, it just appeared solid black. I tried to add a texture file to the materials, but the program would not accept it. The next time I reopened the materials page it was blank again.
-
The magic2 file included with this build seems to have trouble rendering texturs on the 3d models. When I loaded a .mag file, it just appeared solid black. I tried to add a texture file to the materials, but the program would not accept it. The next time I reopened the materials page it was blank again.
I tested this a bit, and it seems there's an issue where Magic tries to load textures from its own directory. So, until this is fixed, you need to place your textures in the same directory the Magic exe is in.
-
Thanks. Tried it, and it worked.
-
Another bug to report (or at least I think it's a bug) is that during the campaign when the player chooses to command a carrier there does not seem to be a way to send attack craft on a planetary strike mission through the flight ops screen. This does not get noticed much because most players do not choose to command the carriers and opt for cruisers instead when they reach high enough rank. It does seem to be real problem though for those who choose to take charge of flight ops in campaign mode.
-
I _think_ that's more of an oversight or feature request than a bug. Not that it matters, I'll add it to the bug list.
-
I _think_ that's more of an oversight or feature request than a bug. Not that it matters, I'll add it to the bug list.
Agreed. I wasn't sure where to post it though and this seemed like the best match. Thank you for adding it to your list. One particular member over at SSC seems to really like being in charge of flight ops and this flaw is particularly bothersome for him. I told him I would refer it to the coding team for consideration.
-
I'm not sure if this is a bug, but I'm having some graphics problems. I am now on my home gaming system instead of my laptop. When I first ran Starshatter this morning it was running at the native resolution setting of my computer which is 1920X1080. I realised that I did not have SSreborn enabled so I enabled it in the mods config section. For some reason my screen resolution changed to 800X600 and now I am completely unable to get it back to 1920X1080. I copied the SSreborn.dat from my laptop which has a max resolution of1024X768 which is what SS now keeps reverting to on my other system. I disabled and then deleted Ssreborn.dat and then reinstalled the newest version of Starshatter, but that did not fix the problem. I thought that Starshatter was now supposed to automatically match the setting of the computer it was installed on, but mine is not doing that for some reason. Any suggestions??
-
Did you run the debug executable by accident? Because that one is hardcoded to only run in 800x600.
-
No, I'm running the correct exe. Just double checked. I'm running Starshatter.exe not the Starshatter_D.exe. I just used an old trick to get my resolution back where I want it. I manually edited the video.cfg and then set it to read only. That appears to have gotten me back to 1920X1080 even though on the config screen it says the game is running in 1024X768. I verified the res by taking a snapshot in game and when I loaded it up in irfanview it did indeed say that the screen shot was 1920X1080. Here is the strange part though. Any time I make ANY changes now in any of the options screens it immediately changes to 800X600 res and I can tell it has actually change just by looking at teh screen. When I exit and restart though it is back where it should be. Is this how it is supposed to run or do I have somethign screwed up? When I go to the video options, the highest res available is 1600X1050 or somethign like that. I know that in a previous version I could select 1920X1080. It's not a big deal because I am able to get it running at the res I want, butit might be a pain for new players to have to go through the video.cfg manual edit.
-
Hmm.
Gonna try and see if I can replicate this.
-
It was that mystery version that fixed this problem but the guy didn't use the SVN. I asked wdboyd if he could get the code from the guy but nothing ever came of it. :(
-
Was that version 5.05 by any chance?
-
It was called 5.0.5 but it was different from the one available at starshatter-open. Wdboyd released it through starshattermods, kind of negating the reason of having a centralized hub for builds.
-
I've encountered this as well. Additionally, the bottom bar of the screen makes my cursor hang up, and I can't move my cursor past that point without exiting the actual game if I click. Makes it a pain to click the Accept, Save, Cancel, etc buttons since only about half of the button is in the part of the screen I can reach.
-
Yeah, the GUI needs a bit of help at extreme limits of the screen. As a temporary workaround, usually holding the cursor over a button, and then pressing enter once the button lights up works, though I think this only tends to work with certain buttons. When you can't get to the cancel, quit, or exit buttons, pressing escape on the keyboard will work sufficiently well also.
-
If you disable desktop compositions it fixes that issue.
-
I think my carrier started shooting itself with its guns. I was playing the carrier vs carrier single mission. I started hearing weapon impacts (but not shots fired), and it looked like the area around my guns were flashing, and I saw that my hull was lower than I remembered it. I couldn't see any enemies nearby that might have been shooting me. Switching guns and pdb from DEF to MAN didn't change anything. Unfortunately the enemy carrier chose that moment to bug out, which automatically ended the mission.
I'd report it as a bug, but I haven't reproduced it yet, and I'm not even sure that's what was happening.
-
Right!
Got the game, grabbed the "new" version of the .exe, set up compatibility mode...
And the game immediately says,
Starshatter cannot open up the file shatter.dat.
And it asks me to do a fresh install.
What should I do?
Edit: Hey guys, ran the debug build, and I've attached what it shot out. Any solutions?
[attachment deleted by a basterd]
-
Ok, heres the dear which pisses me off.
Whenever i complete my mission, i signal Archon to return to base, i get clearing, i get out my landing gear, and confirm my landing.
When im in the fighter bay, camera turns like it was about to finish the mission, but it doesnt, i still controll the ship, and if i don't stop, i just crash into the carrier, dying and failing the mission.
Really bad thing....
-
Thanks for the report, I'll take a look.
-
If im at it, so heres something more:
When you minimize the game, and bring it back up again, and you're using mouse controls for a fighter, it spins around all the time.... just like the mouse were pointing to the edge of the screen.
-
Ok, heres the dear which pisses me off.
Whenever i complete my mission, i signal Archon to return to base, i get clearing, i get out my landing gear, and confirm my landing.
When im in the fighter bay, camera turns like it was about to finish the mission, but it doesnt, i still controll the ship, and if i don't stop, i just crash into the carrier, dying and failing the mission.
Really bad thing....
This is a bit tricky, but I'd call this a feature, and not a bug. But, I do think you ought to have the option of disabling the feature if you don't like it. It might also be nice to have a manual "tower view" mode attached to this feature. Therefore, if you disable the "automatic tower view mode" on final approach, you can still manually toggle it.
-
New bug I'm fixing.
Create Player under the Logbook *should* bring up a screen similar to the first game run screen. I'm changing it so it operates properly - name, empire, physics mode, play style, etc.
-
fixed this bug. Adding and deleting players directly from the logbook now works.
-
Ok, heres the dear which pisses me off.
Whenever i complete my mission, i signal Archon to return to base, i get clearing, i get out my landing gear, and confirm my landing.
When im in the fighter bay, camera turns like it was about to finish the mission, but it doesnt, i still controll the ship, and if i don't stop, i just crash into the carrier, dying and failing the mission.
Really bad thing....
This is a bit tricky, but I'd call this a feature, and not a bug. But, I do think you ought to have the option of disabling the feature if you don't like it. It might also be nice to have a manual "tower view" mode attached to this feature. Therefore, if you disable the "automatic tower view mode" on final approach, you can still manually toggle it.
I'll look into making an auto land feature for the fighter. But I find too many computer controlled fighters love smacking into the rear hull of a ship if the landing bay is in front...
-
I do know that friendly fighters have a tendency to smack into the carrier from time to time - I don't know how much of this is due to the "ship design" code or just the AI code. Otherwise, the ship subsystem settings in the given .def files may have been poorly done - without the carrier fix mod (which I'm not sure is commonly available by itself anymore), fighters AND the player alike tend to smack into the hangar rather than dock, which is a huge problem. The mod fixes this by means of editing/overriding the said .def files. Furthermore, I do have a copy of wdboyd's flight deck tutorial if you need it - this was originally available as the "Modder's Toolkit" before the original Starshatter fan site went down. I might even have the old download file for that particular package as well, if anyone needs it.
-
I have the wdboyd tutorial. Wish I had the source code changes so I can reintegrate it.