3.1.5 known bugs (table on page 1)

posted on March 3rd, 2011, 10:31 pm

noted down

posted on March 3rd, 2011, 11:12 pm

I wouldn't say 'obscured', the Replicators passive doesn't have the code (like the Rhienn special) while the Ion Absorbers uses the wrong location.

posted on March 4th, 2011, 1:34 am

No, that's a bug related to the render if I recall correctly

In that case, it's not on the table on page 1 of this thread.

posted on March 4th, 2011, 2:24 am

There are a lot of background bugs that aren't on the table Doesn't mean they aren't being worked on 

posted on March 4th, 2011, 2:34 am

I was pointing it out because having it one the table prevents a bunch of duplicate bug reports, plus it can get more people aware of how to get control back.

posted on March 4th, 2011, 11:15 am

if u guys describe the bug precisely i can add, im afraid i dont understand the nature of the bug very clearly at present. when does it happen?

posted on March 4th, 2011, 12:59 pm

if u guys describe the bug precisely i can add, im afraid i dont understand the nature of the bug very clearly at present. when does it happen?

So, I guess I didn't describe the bug precisely enough, as it's not in the table.

Summary:
Hardware Vertex Processing and Bump Mapping are always enabled. Unable to save disabled (unchecked) setting across game session.

Description:
By default, the 'Hardware Vertex Processing' and `Bump Mapping' options of graphic settings are checked (enabled). If you unchecked these settings and exit game session, you will find that they are enabled again when you start a new Fleetops session.

How to reproduce:
1. Start Fleetops, go to graphic settings, uncheck 'Hardware Vertex Processing' or 'Bump Mapping' or both.
2. Exit Fleetops.
3. Start Fleetops, go to graphic settings and only to find that these two settings are always checked.

Affected:
1. Fleetops 3.0.0~3.0.7, 3.1.0~3.1.5
2. Windows XP SP3, Windows 7 RTM (x86 and x64), Windows 7 SP1 (x86 and x64)
3. ATI Radeon 9700, X1250, HD5570

posted on March 4th, 2011, 2:27 pm

So, I guess I didn't describe the bug precisely enough, as it's not in the table.

i meant the bug neb was describing. the bug you just mentioned was previously mentioned by someone else, so now i will add it.

posted on March 4th, 2011, 2:33 pm

Basically in addition to what I said before, what is written here as well:
Gameplay and Features - The Hitchhiker's Guide to Fleet Operations

posted on March 4th, 2011, 2:41 pm

Basically in addition to what I said before, what is written here as well:
Gameplay and Features  - The Hitchhiker's Guide to Fleet Operations

ive noted down this as a different bug from building freezing. they could have a similar cause.

posted on March 4th, 2011, 3:01 pm

*adds exception to preventative anti-arguing with myles policy*

The can't select anything bug should not be listed as a freeze, the game actually runs normally except that you cannot select anything (what I've read of the freezing bug says that ships stop moving and the cursor doesn't move either.) You should also include the actions causing it rather than simply say it's not caused by building.

posted on March 4th, 2011, 4:08 pm

lol, things are getting a little tangled now. as far as i know there are 2 bugs, one that causes the interface to stop working when trying to build. that was reported in its own thread.

another, the recently added one, is just randomly freezing, by freezing do you mean that the entire game freezes randomly, not just interface. well thats a very non descript bug lol, any game can randomly stop responding. i'll make a distinction between interface locking up and freezing once its clear which bug is which.

ie does the interface ever lock up other than the building bug?

You should also include the actions causing it rather than simply say it's not caused by building.

what does cause it?

posted on March 4th, 2011, 6:27 pm

The bug that I described is due to the render if I recall, and only locks up the cursor so that you can't click anything. It doesn't affect anything else.

[Dave Denton]

posted on March 4th, 2011, 6:34 pm

Last edited by Dave Denton on March 4th, 2011, 6:38 pm, edited 1 time in total.

Apparently, both Hardware Vertex Processing and Bump Mapping settings are not saved in any configuration files. I checked FOdata.ini and shell.set and they are not changed after unchecked these settings and exit fleetops. As a result, Hardware Vertex Processing and Bump Mapping are always checked when you start a new Fleetops session. Not very friendly for low spec players since uncheck these settings can improve performance a lot.

Applied to: Windows XP SP3 and Windows 7 SP1. I think Windows Vista should be the same.

I agree with you here.

[littletimmy]

posted on March 5th, 2011, 1:30 am

Last edited by littletimmy on March 5th, 2011, 1:34 am, edited 1 time in total.

Well a very unlikely situation, but when you fool around with ai, you may get this... I was assimilating a descent, it had shileds at about 80 perc but thats not the point. As it was almost out of crew descent special kicked in, and i saw a descent with full shields and no crew just floating around. I cant teleport on it since it has shields but it still cant fire on me since it has no crew.Once i got the shields down i could board it as any normal vessel. As you all know, once ship runs out of crew it looses shields.