1.35 bug list |

Sorry people, but the direct draw bug still exist in 1.35.
Re: 1.35 bug list
I didn't have problems so far with 1.35, but "Militians" troops (the ones defending planets with just population) are without weapons... Stock version.

Re: 1.35 bug list
You still can not set ship order in fleets. This is maybe not a bug, but it's a lack of feature which makes the whole fleet system not nearly as useful as it should be.
Re: 1.35 bug list
I attacked the a.i. and it had one armor and one weapon. His armor was low and was easily defeated. The a.i. compensated by putting all armor 4 in this case but leaving out any weapon the next time I attacked. The a.i. needs scripting where it must have weapons in its builds.
Also the a.i. likes to install combat sensors on ships with no weapons, like on freighters.

Re: 1.35 bug list
Right-clicking on a DUC (to see it's properties) on a weapon platform in combat simulator crashes the game.

Re: 1.35 bug list
With 1.35 i've noticed many times that satellites have been built with 3-4 basic sensors. Don't know if thats anything new, but I don't recall seeing satellites with only sensors.
Strategy items not working properly or at all
v.35 BM 1.06
The ability to change items in the strategies has been fixed but the one I tried for Planets with Colonies to attack until all weapons are gone just glasses the planet. I changed all the Strategies to do the above. I don't think there were weapons on the planet down to the last population unit (they started out with 5000M or more) on two different colonies.
Its nice that it can be adjusted. It would be nicer if the settings were actually employed. It worked fine on v.25 BM 1.04 except that the unneeded combat ships would then try to flee the hex, leaving the troop transport unprotected. Can't have everything, I guess.

Re: 1.35 bug list
Doesn't all weapons gone apply only to the attacking ships?
Re: 1.35 bug list
Some problems:
1: stayed the problem, when I want to attack something my fleet may attack anything before reach the target.
2: when I attack a mine field defend planet the end of the battle my ships are retreating, because there are some stayed mine.
3: Anybody seen a attack able drone design by computer?
4: 1.33 or 1.35 version we see, the ruin stayed in the planet after colonization. Why? There are doubled ruin?
Olly.

Re: 1.35 bug list
Yup, got it as well. I've added 3 screen shots with some more info on the message and the state of my machine at the time.

Re: 1.35 bug list
I am unable to change any of the settings that require you to use menu's such as changing screen size.. has anyone else had this problem?
Re: 1.35 bug list
I had some difficulty myself, but then on a lark, I tried doing what it should be doing, and it did fine. No, that doesn't make sense yet. 
I found in trying to change the game setup, such as resolution or hardware card, things like that, when trying to do so it does not indicate when you click something. Apparently, it works fine, you just can't tell without knowing what you set. If you are careful to select your options, it should work fine. It doesn't highlight the text when you select it or open the menu, and it threw me off at first, so it could be the same thing.
If it's something else, I can unfortunately offer no assistance.
Another problem I have is for some reason the title screen causes my mouse to slow down drastically and jump around when I move it. Input is fine, but response is severely slow and choppy. Soon as I open a menu or quit, it is fine though. Just the title screen causes problems.
"Once you have tasted flight, you will forever walk the earth with your eyes turned skyward, for there you have been and will always long to return." ~Leonardo DaVinci

Re: 1.35 bug list
I have the same thing for the ship detail screen (the first you get when you right-click on it) with all the components: the frame rate goes down to 3-5 fps.

Re: 1.35 bug list
Are you sure you're running 1.35? this bug was fixed...
-----
an se5a is a ww1 fighter, it is also a car.

Re: 1.35 bug list
Are you sure you're running 1.35? this bug was fixed...
-----
an se5a is a ww1 fighter, it is also a car.
*DOH* I had downloaded the patch, but then due to failure of my GPU and buying a new one and monitor I hadn't installed the patch.....
Re: 1.35 bug list
here a list of bugs I noticed in 1.35
- Multiplayer TCP Sim. Turns: First Game Turn locks if you generate the Galaxymap in GameOptions
- Multiplayer TCP Sim. Turns: If someone plays on the Host PC, this person needs to end his Turn before everyone else (otherwise their commands wont execute)
- Multiplayer TCP Sim. Turns: in order to load population to your Transports/Colony Ships, "T" for transfer cargo wont be executed, however using "O" load Remote ... works
- I figured out SEV dosnt work with Multi-CPU Systems. That leads to the problem, if you have a Intel CPUs with Hyper-Threading, it only uses half your CPU Power.
You can fix that by disabling Hyper-Threading in your Bios, however the game should work with both as Hyper-Threading and Multi-Core CPUs arent realy uncommon anymore since the new century (you know I mean the year 2000 )

Re: 1.35 bug list
Expected results of techs aren't updated when those techs are received from trade. In my example, I received Military Science level 1 and still showed Defense Systems and Torpedo Weapons as expected results.
Re: 1.35 bug list
Glad to see I'm not the only one with framerate problems.
Latest drivers from nvidia introduced white flashing in the game, which had gone away with a driver set released a month or two ago. I'm thinking it's not Aaron's fault (fault as in blame, but perhaps he could fix it somehow), and have been continuously submitting bug reports to nVidia to try to spur them to fix whatever may be wrong.
Re: 1.35 bug list
Help me out here understanding what you just said if I need it, but are you certain of this? I've been using a Core 2 Duo setup to play, and have had no issues. Admittedly I'm no expert on this sort of stuff, so perhaps I need some educating, but my workstation is running it fine.

Re: 1.35 bug list
This problem isn't unique to SE:V, it's shared by a great number of programs, even current ones. Multi-threaded programming isn't as intuitive as single-threaded programming, but MM is working on it. It may be implemented within a few months.
-----
Space for rent - please contact owner
Re: 1.35 bug list
a Intel Duo-Core CPU shows as 2 CPUs in Windows, if a programm cant handle multi CPU Cores it will only use 1 of them to their max, leading to the programm only using 100% CPU power of 1 of your CPUs.
this means your having your PC being 50% idle, you can watch this if you open Task-Manager during game processing, you will see 1 of your CPUs being at 100% and the other at 0%
if you turn off Hyper-Threading in Bios (which leads to your CPU only showing as 1 in Windows) it will almost double your turn processing speed

Re: 1.35 bug list
in the space empires V/Data folder, open the settings.txt
edit this line:
Support Multithreading := FALSE
to be TRUE.
see if it helps.
(the line is third down from the top)
-----
an se5a is a ww1 fighter, it is also a car.
Re: Strategy items not working properly or at all
Its nice that it can be adjusted. It would be nicer if the settings were actually employed. It worked fine on v.25 BM 1.04 except that the unneeded combat ships would then try to flee the hex, leaving the troop transport unprotected. Can't have everything, I guess.
The transmission seems to be out on this menu.
This is so with the retreat options in the strategies. Ships set to retreat when damaged or when enemy strength is x% continue to fight until all weapons are lost. Out of at least 40 battles, I've seen 2 or 3 actually leave when they should. This may be due to morale or the retreat strategies may be working in a vanishingly small percentage of cases.
I thought perhaps ships were allowed only one retreat parameter, and I set the retreat when weapons gone to False. This didn't help at all. I can find no work-around.
A good feature would be to have a retreat to border and loiter until threatened. I don't know if the retreat to planet or retreat to base are working - haven't tested them intentionally, although I did have some ships set that way for a while.
Edit: Ships are not retreating per menu settings in either BM or stock 1.35.
Re: 1.35 bug list
In my current 1.35 stock game, I've had two reports so far that one of my ships has been damaged by a bomb. I go to the ship, and it's not damaged.
Either this is a bug, or my enemy has tech zero in ship sab and it's supposed to do nothing at tech zero.
The rest of the dirty deeds seem to be working fine so far.
Re: 1.35 bug list
Some problems
- A few times I saw: I had a battle, but later I see the Ordance not decreased (stand the maximum value).
- The fleet name generation stop after "Alfa Eta fleet", drop "Beta fleet" many times, and later drop "Gamma fleet".(I not try after this)
- Under turn begin movement the ship maybe see an enemy ship and turn back, I seen a situation: two warp is blocked, and my ship is move there and back while his movement is lost. What may I do?
Olly.
Re: 1.35 bug list
"Good morning, Pooh Bear," said Eeyore gloomily. "If it /is/ a good morning," he said. "Which I doubt," said he.

Re: 1.35 bug list
This is a big problem that could be dealt with by having a "remembered" FOW. Currently this is crippling to the ai because once a planet is out of sensor range, they think it can be colonized and will send a colony ship. I think that a remembered FOW that has been mentioned in another thread would deal with this problem.
I have actually changed the options so that you don't need sensors (can see all sectors) so the ai can actually have a chance. I have found in my most recent game that the ai seemed a little more challenging in this case.
IMHO, the biggest detriment to the ai is the current FOW system and how the ship ministers are not capable of "remembering" what is where.
Re: 1.35 bug list
Sorry,
This is not a bug, but this is bother me:
When I over researching something, why not change the "1 turn" text to "2/turn" or like this. I think, there is not too difficult to combine the over researching and that technology's max. level.
Olly.
Re: 1.35 bug list
May I ask it: when an Empire has no planet and no ship with Colony Modul or troop cargo, please remove this Empire from the game!
Olly.

Re: 1.35 bug list
Can we come to some sort of consensus about testing for bugs in stock and BM? I thought the "all armor" bug on troops was fixed in BM. Have to check by running a*nothe*r game. And is the BM really an attempt to redress the stock AI, as claimed in "SEV 1.33-worth getting" or is it just an ex official Mod?

Re: 1.35 bug list
Can we come to some sort of consensus about testing for bugs in stock and BM? I thought the "all armor" bug on troops was fixed in BM. Have to check by running a*nothe*r game. And is the BM really an attempt to redress the stock AI, as claimed in "SEV 1.33-worth getting" or is it just an ex official Mod?

Re: 1.35 bug list
Olly.
I second this. To extend this idea further: You could also make the empire die and make the units derelict (i.e. for taking with ship capture) or have them join up with someone.
--------------
What the duck?

Re: 1.35 bug list
Here are some, apologies if duplicate:
1. Fleet AI strategies. The strategy that makes your fleet attempt to disengage every time you try to land troops is EXTREMELY ANNOYING!!! I have been patiently herding them back each time manually, but my patience WILL wear out. Fleets should NOT disengage, under ANY circumstances other than they are too damaged to fight.
2. Just saw this last night. Attacking a planet with a single ship, chose strategic resolution for combat, the planet frikken started MOVING in the sim, trying to get away from the shiP!!!!
The ship was faster, thank god, and caught it and killed it. Man, talk about a Monty Python moment!!!
3. (Minor). When you rename something, it doesn't change the name right away in the display. You have to click something else, and click the renamed object again to see it's new name.
All that is done before the naked stars is remembered
Re: 1.35 bug list
hmmm looks like you have repulsors on your ships.
I guess the repulsor/tractor beams working on planets isn't fixed yet?
Re: 1.35 bug list
I can't even get a game going.
I can set up the game and start it.
However, when I begin playing, and I try to set a production queue - for instance - when I click the "close" button, the whole game minimizes.
Only option then is to close the game.
I am running Athlon XP 2800+
1 GB RAM
250GB drive.
Windows XP Pro SP2 + all updates.
Nvidia Ge Force FX5500 + 256MB.
Has only been happening since 1.35 was installed. Prior patches were not a problem.

Re: 1.35 bug list
Fighters can invade and conquer planets.
This is a bug. I know people like to have them during the assault, but they should not be able to conquer the planet by themselves.
As any grunt will tell you, only 'boots on the ground' take turf, not Starbuck and Apollo landing in their Vipers with laser pistols drawn, to cheering crowds of large breasted blonde women.
All that is done before the naked stars is remembered

Re: 1.35 bug list
Carrier loses Supply attribute.
One of my carriers no longer displays a Supply section in the transfer screen. I can make supplies 'disappear' from my other ships in the same hex by trying to transfer supplies to the carrier, but they never show up for the carrier and the carrier continues to display zero supplies (and no area below to show the supplies, like ordinance).
All that is done before the naked stars is remembered

Re: 1.35 bug list
fighters beign able to take planets is not a bug, it's a feture. you can easly mod it out if you so wish.
-----
an se5a is a ww1 fighter, it is also a car.

Re: 1.35 bug list
don´t know if it´s a new bug but my searches didn´t find it so i just post it....
when you use the "fill construction queue from list" function the max number of facilities limit is not checked.
i made a queue list for a huge planet with 25 facility places and saved it.
i then mistakenly used it on a large planet with 20 facility places and it filled the queue with 25 facilities.
don´t know if there may be a warning when the 20th facility has been constructed (just found that bug so i need some turns) but i guess not.
the same also works on medium and small planets.
can anybody confirm this bug?
happened to me in SEV 1.35 and with BM 1.08 in a new game.
Prankowski

Re: 1.35 bug list
It won't build them and I believe this bug is fixed in the latest beta.
-----

Re: 1.35 bug list
yup, i yesterday played till i reached the limit and then get an error in the news that there is no more space available at the planet.
Re: 1.35 bug list
Intel operations are still performed even if you have zero points allocated. I have 5 communications channels with various races. All but one have zero points allocated towards ops however I still obtain espionage reports regarding the races with zero points allocated every turn.




Re: 1.35 bug list
Have I missed something? Direct Draw bug?
-----
Space for rent - please contact owner