Forums » General
i get the same container error whenever i dock at daltas hold but other than that I find this client works like a dream (except that you guys need to take a class in interface design) but other than that good stuff
hmm weird thing you have there Woodstock, me in F9 A S W D F R are working well, Q E don't work and what are the arrows keys suppose to do because mine don't do a thing.
Linux Kubuntu dapper
Linux Kubuntu dapper
sapo_sk: thanks for the directx9.log file. It looks like the aaquality is very wrong, and preventing the directx window from being opened.
Woodstock: I tried that and like Rygel, my ship didn't move when I pressed the wsad keys.
Woodstock: I tried that and like Rygel, my ship didn't move when I pressed the wsad keys.
My ship definitely moves when I press the w and/or s keys. in Beta 7. On the "Stationary Observer" 3rd person mode (Hit F9 3 times)
w accels it, s decels it, just like normal. Except that it's not supposed to move the ship, but your point of view while in that mode.
w accels it, s decels it, just like normal. Except that it's not supposed to move the ship, but your point of view while in that mode.
Your ship only accels in the 3rd 3rd-person state if you have physics mode off. (I think)
ahh, physics mode off. I'll test that.
I fixed the todo: blahblah message
and the wrong chattab being active when the chat is maximized
and getting damaged during an animation should flash the screen red again, among other things.
I fixed the todo: blahblah message
and the wrong chattab being active when the chat is maximized
and getting damaged during an animation should flash the screen red again, among other things.
ray,
As you suggested, the texture trashing I was describing is less severe when running full screen compare to the reported window-mode trashing I was getting.
So, it's a workaround.
Could I ask that Mac users get a convenient way to switch to other applications when running full screen? Having to switch to other applications is my main reason to run in window (while avoiding reloading all texture on from a mode switch). A hot key to hide the application would be useful, since system-provided ways of doing this are disabled when the menu bar gets hidden (full screen mode).
As you suggested, the texture trashing I was describing is less severe when running full screen compare to the reported window-mode trashing I was getting.
So, it's a workaround.
Could I ask that Mac users get a convenient way to switch to other applications when running full screen? Having to switch to other applications is my main reason to run in window (while avoiding reloading all texture on from a mode switch). A hot key to hide the application would be useful, since system-provided ways of doing this are disabled when the menu bar gets hidden (full screen mode).
Concerning my crash-on-quit when free-floating rather than while docked, it also happens when in full screen mode. The inverse scenario would have surprised me but hey, we never know.
[edited by raybondo: identical crash dump as previous post]
[edited by raybondo: identical crash dump as previous post]
Sorry it took so long to get back to you on this Ray but my problem is the sound driver. I can swap back and forth between the two drivers and get the same result each time.
With alsa I get 19fps on the login screen and with oss I get 380fps at the same screen. Same exact setting everywhere else.
Stranger
With alsa I get 19fps on the login screen and with oss I get 380fps at the same screen. Same exact setting everywhere else.
Stranger
So ray... Any thoughts on the Ready Room change? :P
It got weirder today, could something change within beta7 because now the screen station is much wider then yesterday with 1280*1024
and I didn't change the configuration
http://img54.imageshack.us/my.php?image=vendetta1qi.png
linux Kubuntu dapper
and I didn't change the configuration
http://img54.imageshack.us/my.php?image=vendetta1qi.png
linux Kubuntu dapper
Trying to purchase a saved preset in B7 when the preset is actually empty locked up my client. Well, locked up, in a rather good-natured kind of way. I could click cancel and just return to the station meny, upon which I was told the preset was empty. But as long as I didn't, the client was stuck at the purchasing preset box. No big deal at all, but perhaps something that would confuse newbies when the beta goes production.
Ok, I fixed the empty preset problem and the problem with F9 free-look mode moving your ship if you are also in flight-assist mode.
- when I sold a Ragnarok MkIII, I got the following error:
http://misiorysio.net.pl/dump0000.jpg
The ship had an FC, a Neutron Blaster Mk2, a Mineral Scanner, a Mining Beam and two Locust Swarms (don't ask :P). This happened only once, other non-empty ships sold without problems. When I bought another Ragnarok with such equipment, it sold without problems as well.
- when you try to buy more than 5 pieces of any ship equipment, a "todo: display error: error giving item" message appears.
- error messages, such as the one above, seem to have the color of the last message before it:
http://misiorysio.net.pl/dump0001.jpg
http://misiorysio.net.pl/dump0000.jpg
The ship had an FC, a Neutron Blaster Mk2, a Mineral Scanner, a Mining Beam and two Locust Swarms (don't ask :P). This happened only once, other non-empty ships sold without problems. When I bought another Ragnarok with such equipment, it sold without problems as well.
- when you try to buy more than 5 pieces of any ship equipment, a "todo: display error: error giving item" message appears.
- error messages, such as the one above, seem to have the color of the last message before it:
http://misiorysio.net.pl/dump0001.jpg
misiorysio: "- when you try to buy more than 5 pieces of any ship equipment, a "todo: display error: error giving item" message appears."
I was unable to reproduce this.
I was unable to reproduce this.
Not sure if that's new in this release but, everytime I mine a unit the game makes a small hickup. It's hardly noticable if you don't pay attention.
linux2.6.15/xorg7/alsa/gforce2mx
EDIT: hmm ... not only while mining ..everytime somethign happens I get a hickup. And it seems to get worse the longer the game runs.
linux2.6.15/xorg7/alsa/gforce2mx
EDIT: hmm ... not only while mining ..everytime somethign happens I get a hickup. And it seems to get worse the longer the game runs.
groups still don't work
some really weird crap happens if you try to re-purchase a ship after being destroyed and not all of the equipment you had on it is saleable at the station (even if it is stockpiled there)
Last time it happened to me, the ship changed color (to white) and equipped only the battery and a Gat Turret (one of the two items that was not available at the station, but stockpiled there) while the other unavailable item, as well as the available one were not equipped.
grouping still does not work (on the Radar)
Some ships are misidentified both in the sector list and on the HUD when targeted (example: targeting one of the turrets on a capship gave the name of the capship, Arena Seekers were labeled as "Station Guard" or "Strike Force", etc...)
if entering the navmap while holding down the tab (turbo) key, the chat area is put in focus, and a return /msg prepped. Firther keystrokes (like n, to exit the menu) are caught by the chat, and then autocompleted to player names)
green
F9 while holding tab generates Lua error
sector list (u) while holding brakes (space) causes the sector list to flicker in and out rapidly
several other combinations of holding down keys (wasdrf, tab, space) while bringing up menus of different sorts cause oddities or even Lua errors.
Station menu is confusing as ever... just thought I'd throw that out there.
I still get health bar shrinkage when grouped.
there are various discontinuities between the sector list and radar.
There is a formidible delay between when something is targeted and when your HUD tells you what it is.
there seems to be some kind of odd targeting priority, such that asteroids are easier to select than cargo, and cargo easier to select than vessels. It is also extremely difficult to change from targeting one thing in front of you to another unless you can deselect everything first using (x). The most defining phenomenon of all this is that what you select with (b) isn't always the thing closest to your center of vision, and it's almost always not what you want.
some really weird crap happens if you try to re-purchase a ship after being destroyed and not all of the equipment you had on it is saleable at the station (even if it is stockpiled there)
Last time it happened to me, the ship changed color (to white) and equipped only the battery and a Gat Turret (one of the two items that was not available at the station, but stockpiled there) while the other unavailable item, as well as the available one were not equipped.
grouping still does not work (on the Radar)
Some ships are misidentified both in the sector list and on the HUD when targeted (example: targeting one of the turrets on a capship gave the name of the capship, Arena Seekers were labeled as "Station Guard" or "Strike Force", etc...)
if entering the navmap while holding down the tab (turbo) key, the chat area is put in focus, and a return /msg prepped. Firther keystrokes (like n, to exit the menu) are caught by the chat, and then autocompleted to player names)
green
F9 while holding tab generates Lua error
sector list (u) while holding brakes (space) causes the sector list to flicker in and out rapidly
several other combinations of holding down keys (wasdrf, tab, space) while bringing up menus of different sorts cause oddities or even Lua errors.
Station menu is confusing as ever... just thought I'd throw that out there.
I still get health bar shrinkage when grouped.
there are various discontinuities between the sector list and radar.
There is a formidible delay between when something is targeted and when your HUD tells you what it is.
there seems to be some kind of odd targeting priority, such that asteroids are easier to select than cargo, and cargo easier to select than vessels. It is also extremely difficult to change from targeting one thing in front of you to another unless you can deselect everything first using (x). The most defining phenomenon of all this is that what you select with (b) isn't always the thing closest to your center of vision, and it's almost always not what you want.
RelayeR - that's weird, I just checked and it still happens for me.
Another bug - when you click on the field where you enter the number of things to buy, the cursor appears before the "1", but when you type in something it jumps to after the "1". I have caught myself a few times pressing Delete to remove this "1" and wondering why nothing happened.
Another bug - when you click on the field where you enter the number of things to buy, the cursor appears before the "1", but when you type in something it jumps to after the "1". I have caught myself a few times pressing Delete to remove this "1" and wondering why nothing happened.
Minor bug, just a curiosity but did make me pause, and I hit upon it by chance.
In the mission tab, choose a mission, click info, and then decline. Then click on another mission; now both missions are highlighted in the mission menu. That's it; there's nothing beyond that, but when I saw it I had a vision of two missions trying to talk at once and VO crashing. This was in the Windoze version, as usual.
In the mission tab, choose a mission, click info, and then decline. Then click on another mission; now both missions are highlighted in the mission menu. That's it; there's nothing beyond that, but when I saw it I had a vision of two missions trying to talk at once and VO crashing. This was in the Windoze version, as usual.
jex: I've had that happen in Linux client, too.