that's all well and good. frankly, that's the way I figured the route through deferra worked. it was actually a warp corridor above or below fed space.
but that's not there any longer and the game engine makes poor use of the z-axis. the autonav cant even handle the concept.
respectfully taco, its fine for high level players those with full diplomatic access to go wherever they want, but the borders should still exist in the game. and even for those higher level players, there still ought to be acknowledgement that you are crossing boarders.
We don't have time to make a bunch of specialty stars, unfortunately. But the systems we have in game don't orbit any anyway, so I don't think it's a huge deal.
No, but it would be cool to have some of these "special" phenoma visible. It's a tiny bit of exploration, rewarding people to actually fly to the different systems and looking more closely what's going on. But if the time isn't there, the time isn't there.
There is some system (I'll have to look it up when I'm back at work) which is supposed to have a Neutron star orbiting a main sequence I think. But we chose not to represent the Neutron because Neutron stars are so tiny.
But also very dense - neutron stars with a main sequence partner are "supected" culprits behind at least one type of (super?)nova*. The neutron star sucks off gas from its partner, and at some point he basically ignites that gas and creates a runaway nuclear reaction that shines brightly.
Considering the tiny size of a neutron star, you'd probably in space only see the stream of gas going to seemingly nowhere.
)* I think I read articles on this several times, but I can't seem to get straight what when qualifies for a supernova and what for nova. And I am too lazy to look it up again.
Star Trek Online Advancement: You start with lowbie gear, you end with Lobi gear.
We don't have time to make a bunch of specialty stars, unfortunately. But the systems we have in game don't orbit any anyway, so I don't think it's a huge deal.
There is some system (I'll have to look it up when I'm back at work) which is supposed to have a Neutron star orbiting a main sequence I think. But we chose not to represent the Neutron because Neutron stars are so tiny.
My number 1 request is PLEASE let us zoom out farther. I like the look of flying with astrometrics on holodeck, but the astrometrics on tribble seem larger, and that combined with the close in zoom limit almost hurts my eyes to look at.
DO you think you could adjust the AQ map to put a blue mist in the background of the Betazed sector? I know it was occupied during the Dominion war but my understanding is that it was retaken shortly after the tide changed so it really shouldn't be in a Border/Cardassian area.
DO you think you could adjust the AQ map to put a blue mist in the background of the Betazed sector? I know it was occupied during the Dominion war but my understanding is that it was retaken shortly after the tide changed so it really shouldn't be in a Border/Cardassian area.
personally, I think fed/cardassian space should basically be bordered through between bajor and cardassia. there is a REASON its Deep Space 9. its on the extreme outer limit of fed space, though bajor is definitely the closest "outer limit" of federation space to earth.
maybe, it should be considered in the not too distant future to have a gamma quadrant other than in a mission. could have fun with it and force all but max diplo players to go to ds9 and get authorization for wormhole transit.
During the discussion, Janeway pauses periodically to gaze toward the Ready Room's wide, transparent aluminum windows, through which we can both see the faint, rhythmic oscillations of the Hobus Cinder through the distortion of the nebula's amber haze. the supernovas'a gradually cooling corpse seems to twitch metronomically, pulsating like a distant, sinister heartbeat. The effect is both horrific and hypnotic.
I'm currently parked over the Hobus star system on the sector map. Can I assume that the gorgeous sun I see there presently, is merely a stand-in for art consistent with the novels description to come later?
(/\) Exploring Star Trek Online Since July 2008 (/\)
Feedback on sector space revamp after the Tribble patch on March 20, 2015
1. There are multiple problems with camera zoom.
(a) The default maximum camera distance in sector space is 12. I cannot zoom out farther than this using the mouse wheel. I can set the camera distance to 35 using the command "/camdist 35", but the camera tends to zooms back in. Sometimes, the camera zooms back in immediately. If not, then attempting to zoom out any farther using the mouse wheel will make the camera zoom in. Viewing the ship from certain angles also causes the camera to zoom back in. The user can inadvertently stumble upon such an angle just by looking around.
(b) Ships have been scaled down in sector space. At the same camera distance, a ship looks smaller in sector space than in system space. This breaks keybinds that use the command /camdist to set the camera distance. Before the sector space revamp, I could use the same keybinds for system space and sector space. I now need twice as many keybinds, because ships are different sizes in system space and sector space.
(c) Upon entering a system from sector space, your ship looks huge, because the camera distance remains the same but ships are much larger in system space.
(d) When the user beams up from the ground to system space or sector space, the camera zooms in very close to the ship. This particular bug dates back to Season 6.
Camera zoom has been QoL issue since Season 6. It will get worse with the sector space revamp if you do not fix these problems before Season 10 goes live.
2. There are multiple problems with doff assignments in sector space.
(a) There are fewer assignments under "Current Map", but more assignments under the department heads. Some people have claimed that assignments which used to appear under "Current Map" are showing up under the department heads.
(b) New assignments appear and then disappear in the "Current Map" tab. Sometimes, it happens as I cross a sector border. Other times, it happens in the middle of a sector. I've also seen the assignment list change as I cross into a new sector, but when I go back to the sector I came from, the assignment list does not change back.
(c) The department heads behave strangely when you cross a sector border. For example, if you cross a sector border while viewing assignments from the first officer, old assignments disappear but new assignments don't show up. To force the new assignments to show up, you have to click "Department Heads" again and reselect the first officer. The operations department head does not refresh automatically when you cross a sector border. To force a refresh, you have to click "Department Heads" again and reselect the operations department head.
3. In general, it has been a frustrating experience testing the doff system on Tribble, because it's not clear how things are supposed to work. It would help greatly if a developer would answer the following questions:
(a) Is each sector supposed to have separate assignments, or are sectors grouped together for doffing purposes like the old sector blocks? If sectors are grouped, then give us a map showing which sectors are grouped together.
(b) Which assignments are supposed to appear in which sectors? Give us a data dump with the following information for each assignment:
assignment name
rarity
maps and sectors where the assignment appears
tabs in the doff UI where the assignment appears
4. There are multiple problems with "Tour the Galaxy".
(a) The timer does not count down unless you move your mouse over it or complete an objective. The same problem occurs with the old "Tour the Galaxy" on Holodeck.
(b) The blog post said we would have more time to complete the Tour, but the time limit is still 15 minutes.
(c) With max driver coil and the Borg engine, I can complete the old "Tour the Galaxy" in 11 minutes with 4 minutes to spare. I could not complete the new "Tour the Galaxy": it took me 14 minutes and 30 seconds just to finish the Beta Quadrant.
(d) My ship spun out of control during "Tour the Galaxy". It would not stop turning until I logged the character out. This has happened to me three times so far. Here's a video of the bug.
It's possible that the bug is unrelated to "Tour the Galaxy". I suspect the bug may be caused by turning while in slipstream.
(e) The auto-pilot sometimes stops too far away from the destination, so you have to move slightly in order to the complete objective.
(f) The stars and other objects, such as asteroids and stations, are too big and frequently get in the way. Several times, I found my path blocked by obstacles. I had to back up or fly around the obstacles before continuing. I suggest changing the Tour so that the player needs to pass through certain sectors rather than visit certain systems. This change would allow the player to plot a course away from the obstacles in sector space.
5. The huge stars frequently block the path to a system's entrance. The auto-pilot stops you right next to the star, which may put you out of range of the entrance. Whether you're in range or not largely depends on the direction from which you approach the system. If you approach from the side opposite the entrance, then you need to maneuver around the star to reach the entrance. This problem can be seen in the systems below. Each of these systems contains a patrol---the first two at planets and the third at an asteroid belt. In all three cases, the star blocks the path to the entrance if you approach the system from the wrong side.
In the last example, even though I clicked on Bajor, the auto-pilot stopped me next to the star right outside DS9.
6. The stars expand to a size that makes them look very close to your ship. But in most cases, a player's purpose in visiting a star system is to establish orbit around a planet or dock at a space station, not take close-range sensor readings of the system's star. For example, the destination of a player who visits the Sol System is likely Earth Spacedock or Starfleet Academy. But in sector space, Sol appears much larger than it would if viewed from Earth. The following screenshot was taken near Earth orbit in sector space:
As you can see, the sun blocks most of my screen. Does the real sun look that big to you when you look up at the sky?
7. I saw a deep space encounter named "Deep Space Encounter: Intelligence Disaster" on the border between the Archanis Sector and the Gamma Eridon Sector. On a federation character, the deep space encounter kept flashing---appearing one moment and disappearing the next. On a KDF character, the deep space encounter did not flash, but there was no prompt to enter it.
8. The icons for systems, stations, and clusters look too big on the mini-map. I suspect that the icons are using a different scale from the rest of the mini-map. For example, when the mini-map is scaled to 50%, the icons are scaled to only 90%. These are not the exact percentages, but something similar must be happening. It's possible that the icons are using the scale for main map instead of the scale for the mini-map. The same problem appears on Holodeck, but it's more noticeable on Tribble because there are more systems. Take a look at the screenshots below. They were taken after zooming the mini-map to maximum size and then clicking the minus button 30 times.
9. When you fly near the border between quadrants, a window with your boff pops up asking if you would like to cross the border. Consider replacing the pop-up window with a simple button that says "Enter the XYZ Sector". I don't need a boff asking me whether I want to cross what should be a contiguous region of space.
10. The names of sector blocks in the mission text have been replaced with the names of quadrants. Since the quadrants are quite big, it would be more helpful to say something like "Go to the ABC System in the XYZ Sector of the Alpha Quadrant."
11. The transwarp list still refers to the "Tau Dewa Sector Block" and the "Delta Sector Block". Also, the order of the transwarp list on Tribble is different from the one on Holodeck.
12. The "Beam Up" window at Starfleet Academy still refers to the "Sirius Sector Block". The "Beam Out" window at Klingon Academy still refers to the "Omega Leonis Sector Block". The "Beam Up" windows on Defera and the Defera Invasion Zone still refer to the "Deferi Sector Block". If you beam up from Defera or the Defera Invasion Zone to sector space, the system first sends you the Orellius Sector Block before sending you the Alpha Quadrant.
13. The beam-in and warp-in animations are broken, though the beam-out and warp-out animations still work. Also, the screen flashes when you beam down to Starfleet Academy or Klingon Academy: it looks as though you enter the map twice.
14. The visual effects are smaller now, but they still look wrong. Compare the screenshots below.
15. Before Legacy of Romulus, quantum slipstream drive would continue even after you cross into a new sector block. This was broken in Legacy of Romulus. Now, crossing the border between quadrants cancels quantum slipstream drive.
17. The tray forgets the position of the MACO 3-piece bonus Heavy Graviton Beam. If you swap the MACO engine for the Borg engine and then swap them back again, the tray does not place the icon for Heavy Graviton Beam back in its original position. On Holodeck, the tray remembers the position of Heavy Graviton Beam.
18. The commands "/showfps 1" and "/showCamPos 1" no longer work. They are broken in sector space, in system space, and on the ground.
19. Please consider bringing back Tribble Weekend in order to test the system under heavy load.
BOff contacts (e.g., warp to next Quadrant, navigation info, red alert notifications) are erroneously displayed with a viewscreen frame (although they are supposed to be on your own bridge) and without or the wrong bridge background (Galaxy-style and not Origin style for FED).
Delta Quadrant: The Milky Way background is on the wrong side. It currently points out of the galaxy, and not towards its center!
BOff contacts (e.g., warp to next Quadrant, navigation info, red alert notifications) are erroneously displayed with a viewscreen frame (although they are supposed to be on your own bridge) and without or the wrong bridge background (Galaxy-style and not Origin style for FED).
Delta Quadrant: The Milky Way background is on the wrong side. It currently points out of the galaxy, and not towards its center!
frtoaster mentioned almost everything I wanted to post (and more).
Except some details:
Doffing: The cluster contacts often offer no assignements at all (For instance, clicking on the Rolor Nebula contact resulted in showing me an empty tab.).
Transwarps:
- The Tuffli and Suliban Cell miss almost all transwarps to clusters. Under the header 'Zenas Expanse', the three former Cardassian space clusters are shown. All other clusters seem to have transwarps missing.
- The transwarps gained by ranking up the Diplomacy/Marauding tracks don't show up reliably. One of my KDF characters was missing transwarps to Alpha Centauri and Regulus. A Federation character, on the other hand, seemed to receive all of the transwarps correctly.
Beam up:
- beaming up from Qo'nos system lead to my ship appearing in sector space above Boreth, not Qo'nos. Some 2 (or 4, was it?) light years away.
Overall, I'd like to stress the importance of fixing the camera distance trouble. On holodeck, you only have to set your desired camera distance upon beam up from a ground map (not always, but very often). On Tribble, due to the difference of ship sizes from system to sector, the camera distance also always resets when entering system space from sector (zooming in on your ship that becomes so much larger). In addition to that, the maximum camera distance in sector is still too small: larger ships (like the Kar'fi carrier or tuffli freighter) will still take up a large part of the screen at maximum distance, despite their scaling down.
And yes, I'm fast becoming far less of a fan of the huge stars. They're actually far more annoying than huge Scimitars blocking our paths on Holodeck. What would help? Obviously scaling them down somewhat. And also, making the auto travel move us always on top of the stars/planets/bases. That way, we'd no longer have to fly around them every time auto travel gets us right next to them.
TOIVA, Toi Vaxx, Toia Vix, Toveg, T'vritha, To Vrax: Bring in the Allegiance class. Toi'Va, Ti'vath, Toivia, Ty'Vris, Tia Vex, Toi'Virth: Add Tier 6 KDF Carrier and Raider. Tae'Va, T'Vaya, To'Var, Tevra, T'Vira, To'Vrak: Give us Asylums for Romulans.
I have a problem with the positioning of a few area's and these are based on common sense and the movies/TNG which despite whatever maps people have extrapolated the movies are canon.
1 Nimbus System, in Star Trek V, The Romulan Ambassador says that the 3 governments agreed to jointly develop Nimbus III, Why would the Klingon Empire bother with this if the system lay between the Romulan Empire and the Federation??? quite simply put they wouldn't.
Surely a better place would be the Bottom part of Japori or Azure sectors.
2. Mutara Nebula I know the books and other stuff says it should be south of Klingon space but there's a huge problem. Why would the federation have a research facility in orbit of Regulus next to the Mutara Nebula if it is so far away from Federation space? They wouldn't the security risks would be too great, not to mention in Star Trek II the Enterprise gets there relatively quickly so it wouldn't be that far from Earth probably close to the Klingon Border but not where it has been put.
Better solutions Kassae Aldebran or Ba'aja Sectors.
3.Galorndon Core, it's supposed to be in the Neutral zone between the Federation and Romulan empires not on the far right hand edge of the map, it just seems too far over.
Surely moving it 1 or 2 sectors to the left might make more sense.
Just my suggestions, I don't know how others feel but there ya go.
Other than that I like the feel, yeah still a couple of walls but fewer issues loading. I can actually point and click and the go make a drink, come back an I'm there which is good
I'm loving the whole system enlargement as you approach, it gives you an appreciation or scale. Star Trek now looks BIG as it was meant to be :cool:
Hey Taco, can you give us an answer about moving Nimbus? It just seems like it should be near Rom, Fed, and Klingon space instead of being so far north.
"The soldier above all others prays for peace, for it is the soldier who must suffer and bear the deepest wounds and scars of war."
Douglas MacArthur - Quote on the dedication plaque of the U.S.S. Ranger NCC-97332-A Armitage class Fleet Heavy Strike Wing Escort.
Seen it. But I have herd people question how accurate it is. Don't know my self. The biggest question is why would the Klingons agree to jointly develope a planet so far away.
The inpression that I got was it was near all three borders.
"The soldier above all others prays for peace, for it is the soldier who must suffer and bear the deepest wounds and scars of war."
Douglas MacArthur - Quote on the dedication plaque of the U.S.S. Ranger NCC-97332-A Armitage class Fleet Heavy Strike Wing Escort.
Seen it. But I have herd people question how accurate it is. Don't know my self. The biggest question is why would the Klingons agree to jointly develope a planet so far away.
The inpression that I got was it was near all three borders.
Who says it's far away? You're looking at a 2D map representing 3D space, Klingon space could very well border that area between the Romulan and Federation Neutral Zone. It's the same with dialogue said on DS9 where Romulan ships struck Cardassian outposts along the border with their space.
Who says it's far away? You're looking at a 2D map representing 3D space, Klingon space could very well border that area between the Romulan and Federation Neutral Zone. It's the same with dialogue said on DS9 where Romulan ships struck Cardassian outposts along the border with their space.
We're playing a game with a 2D map, so unfortunately it needs to conform to how it is laid out, not only so it looks right but for the sake of common sense.
There's no rules that say it has to conform to a map that someone extrapolated, this person could have made a mistake clearly this is the case with the locations of some of these systems. STO devs have a chance to put them right afterall it's their game, I'm sure they'll get more flak from others when it goes live if things remain where that are, best to change them now and not have to move them later.
Hey Taco, can you give us an answer about moving Nimbus? It just seems like it should be near Rom, Fed, and Klingon space instead of being so far north.
Seen it. But I have herd people question how accurate it is. Don't know my self. The biggest question is why would the Klingons agree to jointly develope a planet so far away.
The inpression that I got was it was near all three borders.
I've been over this numerous times already. No, Nimbus is not being moved.
The so called "Planet of Galactic Peace" was a poorly planned joint venture that none of the sides cared much about. We don't know the details about it's creation, but given that each faction used it as a dumping ground for their less savory citizenry, I think it's fair to assume that none of them really cared where it was. In fact, the Klingons may have been happy to have it farther away from them. Who knows.
What I do know, is that that's where Star Charts puts it, and that's what we're trying to follow here. We can (and apparently do) argue about it all day long, but there are much larger fish to fry.
Yeah, like Sol being incorrectly placed in the Beta quadrant!
:P
Just playing, I know it's always been there, all this bickering about planet placement is just very funny to me, lol.
Kind of makes you wonder why they are referred to as the Alpha Quadrant powers, when most of them reside in the Beta Quadrant, yet another weird thing in the Star Trek universe :P
Perhaps they should have employed someone to draw a map for them as they were making the series and stick everything on it correctly, I'm guessing during the 60's they had no budgedtor were stoned :P probably both.
Kind of makes you wonder why they are referred to as the Alpha Quadrant powers, when most of them reside in the Beta Quadrant, yet another weird thing in the Star Trek universe :P
Perhaps they should have employed someone to draw a map for them as they were making the series and stick everything on it correctly, I'm guessing during the 60's they had no budgedtor were stoned :P probably both.
I forgot where I read it (maybe io9.com or something), but someone looked over the episodes of TOS and realized that some of the "Away Team missions" were them just walking over to the sets of other shows happening near the filming stage. Aka, the Westerns, time travel, and the episodes about alternate earths.
So, budget was a bit "tight".
Member since November 2009... I think. (UFP) Ragnar
It would make more sense to have all of the Doff missions in a quadrant available to select from in the doff UI rather than by sector as is now.
I can imagine this is a sticky design issue and there very well my be some drawbacks to viewing and selecting from such a large list but the current theory of trying to keep the doff missions separated by sector really aren't working fluidly for me (an others I assume). The recent changes to the doff UI - allowing a streamlined view of doff missions - could overcome that burden.
Is it possible to at least offer a one week test of this change to see how viable it is? It's a gamble for sure but if doffing rolls out the way it is now I guarantee you will find yourself making changes to its function soon enough. The logic which is being applied now makes sense in a sector isolated map design since I will always know what sector I'm in and cannot move between sectors without manual involvement. With a more open map sectioned by quadrant that design theory loses its relevance.
It's obvious your are working under the requirement of showing a manageable list of missions to the player by moving a majority of the missions under first officer recommendations to no clutter the main screen but this requirement is forcing bad design and a lower QoL in my opinion (for one it muddles which missions are sector specific and which ones are first officer recommendations specific - one group is static while the other is not). I'm not afraid of a large list, especially with the redesign of the doff UI it's not unmanageable.
One way could be removing some doff missions. I am not referring to any of the chained missions, personal missions or first officer recommendations, or the special higher quality sector only missions but to the list of available standard common missions that offer no additional award other than basic mats/dil/xp/commendation. If you indeed move to show all missions for a given quadrant there is only a certain amount of missions one captain can assign at a time. This way we leave missions where they are now with the personal and first officer assignments screens not seeing an increase and with the main ui screen showing an increase in listed missions by something like 100-125% (so double the size of the current list or a little more). So instead of seeing 3-5 science missions awarding mats it might now be 10-15 (of course you would need to adjust the numbers to accommodate those who assign more than 20 missions). That should provide a much more manageable list than providing all of the current doff missions available in an entire quadrant. Again, as long as you don't remove the special doff missions and only reduce numbers in the common non chained missions no one should miss anything. You won't be able to assign all of the missions anyway.
I've been over this numerous times already. No, Nimbus is not being moved.
The so called "Planet of Galactic Peace" was a poorly planned joint venture that none of the sides cared much about. We don't know the details about it's creation, but given that each faction used it as a dumping ground for their less savory citizenry, I think it's fair to assume that none of them really cared where it was. In fact, the Klingons may have been happy to have it farther away from them. Who knows.
What I do know, is that that's where Star Charts puts it, and that's what we're trying to follow here. We can (and apparently do) argue about it all day long, but there are much larger fish to fry.
Thanks for the response. Did not mean to make you repeat yourself. I looked but did not find a Dev response about Nimbus.
"The soldier above all others prays for peace, for it is the soldier who must suffer and bear the deepest wounds and scars of war."
Douglas MacArthur - Quote on the dedication plaque of the U.S.S. Ranger NCC-97332-A Armitage class Fleet Heavy Strike Wing Escort.
I forgot where I read it (maybe io9.com or something), but someone looked over the episodes of TOS and realized that some of the "Away Team missions" were them just walking over to the sets of other shows happening near the filming stage. Aka, the Westerns, time travel, and the episodes about alternate earths.
It's not as random as it sounds. It's a matter of studio. TOS was produced by Desilu. Desilu (owned by Lucille Ball, yes, Lucy, from I love Lucy) owned the sets for the Andy Griffith show, so it was simply a matter of scheduling their use.
Kind of makes you wonder why they are referred to as the Alpha Quadrant powers, when most of them reside in the Beta Quadrant, yet another weird thing in the Star Trek universe :P
Perhaps they should have employed someone to draw a map for them as they were making the series and stick everything on it correctly, I'm guessing during the 60's they had no budgedtor were stoned :P probably both.
and i personally think that they just call themselves the "Alpha Quadrant powers". its technically not the "Alpha" Quadrant, but no one questions it. Kinda like how the Dallas Cowboys have never once had a stadium that was actually in Dallas, with the old Texas Stadium being in Irving and the current AT&T Stadium being in Arlington
there are other examples of this but i couldn't think of them
I mean....who wants to be a Beta Quadrant power? sounds kinda second best
EDIT: took me FOREVER to find that post! we have DevTracker. what do we need to do to make a MeTracker?
Kind of makes you wonder why they are referred to as the Alpha Quadrant powers, when most of them reside in the Beta Quadrant, yet another weird thing in the Star Trek universe :P
Perhaps they should have employed someone to draw a map for them as they were making the series and stick everything on it correctly, I'm guessing during the 60's they had no budgedtor were stoned :P probably both.
Well didn't most of the referencing take place during DS9? I wouldn't be surprised for that show if they went with "Alpha" over "Beta" just for the sake of a better sounding line (which you could try to justify by the fact that the FED is spread on through part of the AQ, ignoring for the moment the ROM and KDF....)
Also, one bit of Sector revamp feedback. Max zoom (towards ship) causes the player ship (or to be more specific if its not a universal problem, my Ma'Tha raptor) to disappear from some angles. Shuttles have had the same problem for quite some time (and it is quite annoying for those that like to appreciate details).
Bipedal mammal and senior Foundry author.
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
Comments
that's all well and good. frankly, that's the way I figured the route through deferra worked. it was actually a warp corridor above or below fed space.
but that's not there any longer and the game engine makes poor use of the z-axis. the autonav cant even handle the concept.
respectfully taco, its fine for high level players those with full diplomatic access to go wherever they want, but the borders should still exist in the game. and even for those higher level players, there still ought to be acknowledgement that you are crossing boarders.
But also very dense - neutron stars with a main sequence partner are "supected" culprits behind at least one type of (super?)nova*. The neutron star sucks off gas from its partner, and at some point he basically ignites that gas and creates a runaway nuclear reaction that shines brightly.
Considering the tiny size of a neutron star, you'd probably in space only see the stream of gas going to seemingly nowhere.
)* I think I read articles on this several times, but I can't seem to get straight what when qualifies for a supernova and what for nova. And I am too lazy to look it up again.
So, no chance of seeing pulsars, or even binary pulsars, then. :P
Commanding Officer: Captain Pyotr Ramonovich Amosov
Dedication Plaque: "Nil Intentatum Reliquit"
The-Grand-Nagus
Join Date: Sep 2008
he didn't say that. It's just that we wont see them at release. Doesn't mean that eventually it'd be updated to allow for those stars
personally, I think fed/cardassian space should basically be bordered through between bajor and cardassia. there is a REASON its Deep Space 9. its on the extreme outer limit of fed space, though bajor is definitely the closest "outer limit" of federation space to earth.
maybe, it should be considered in the not too distant future to have a gamma quadrant other than in a mission. could have fun with it and force all but max diplo players to go to ds9 and get authorization for wormhole transit.
I'm currently parked over the Hobus star system on the sector map. Can I assume that the gorgeous sun I see there presently, is merely a stand-in for art consistent with the novels description to come later?
1. There are multiple problems with camera zoom.
(a) The default maximum camera distance in sector space is 12. I cannot zoom out farther than this using the mouse wheel. I can set the camera distance to 35 using the command "/camdist 35", but the camera tends to zooms back in. Sometimes, the camera zooms back in immediately. If not, then attempting to zoom out any farther using the mouse wheel will make the camera zoom in. Viewing the ship from certain angles also causes the camera to zoom back in. The user can inadvertently stumble upon such an angle just by looking around.
(b) Ships have been scaled down in sector space. At the same camera distance, a ship looks smaller in sector space than in system space. This breaks keybinds that use the command /camdist to set the camera distance. Before the sector space revamp, I could use the same keybinds for system space and sector space. I now need twice as many keybinds, because ships are different sizes in system space and sector space.
(c) Upon entering a system from sector space, your ship looks huge, because the camera distance remains the same but ships are much larger in system space.
(d) When the user beams up from the ground to system space or sector space, the camera zooms in very close to the ship. This particular bug dates back to Season 6.
Holodeck ticket #3,271,917: Camera zoom bug from Season 6
The only difference now is that the camera distance is set to 12 instead of 35 when the user beams up from the ground to sector space.
Please see the following thread for details:
Technical details regarding problems with zoom
Camera zoom has been QoL issue since Season 6. It will get worse with the sector space revamp if you do not fix these problems before Season 10 goes live.
2. There are multiple problems with doff assignments in sector space.
(a) There are fewer assignments under "Current Map", but more assignments under the department heads. Some people have claimed that assignments which used to appear under "Current Map" are showing up under the department heads.
(b) New assignments appear and then disappear in the "Current Map" tab. Sometimes, it happens as I cross a sector border. Other times, it happens in the middle of a sector. I've also seen the assignment list change as I cross into a new sector, but when I go back to the sector I came from, the assignment list does not change back.
Tribble ticket #49,426: New assignments disappear when ship crosses sector border
Tribble ticket #49,427: Assignment list does not change when ship crosses sector border
Tribble ticket #49,430: Assignment list changes in the middle of the Bajor Sector
(c) The department heads behave strangely when you cross a sector border. For example, if you cross a sector border while viewing assignments from the first officer, old assignments disappear but new assignments don't show up. To force the new assignments to show up, you have to click "Department Heads" again and reselect the first officer. The operations department head does not refresh automatically when you cross a sector border. To force a refresh, you have to click "Department Heads" again and reselect the operations department head.
Tribble ticket #49,428: New assignments from first officer do not show up when ship crosses sector border
Tribble ticket #49,429: Department heads do not refresh when ship crosses sector border
3. In general, it has been a frustrating experience testing the doff system on Tribble, because it's not clear how things are supposed to work. It would help greatly if a developer would answer the following questions:
(a) Is each sector supposed to have separate assignments, or are sectors grouped together for doffing purposes like the old sector blocks? If sectors are grouped, then give us a map showing which sectors are grouped together.
(b) Which assignments are supposed to appear in which sectors? Give us a data dump with the following information for each assignment:
assignment name
rarity
maps and sectors where the assignment appears
tabs in the doff UI where the assignment appears
4. There are multiple problems with "Tour the Galaxy".
(a) The timer does not count down unless you move your mouse over it or complete an objective. The same problem occurs with the old "Tour the Galaxy" on Holodeck.
(b) The blog post said we would have more time to complete the Tour, but the time limit is still 15 minutes.
(c) With max driver coil and the Borg engine, I can complete the old "Tour the Galaxy" in 11 minutes with 4 minutes to spare. I could not complete the new "Tour the Galaxy": it took me 14 minutes and 30 seconds just to finish the Beta Quadrant.
(d) My ship spun out of control during "Tour the Galaxy". It would not stop turning until I logged the character out. This has happened to me three times so far. Here's a video of the bug.
https://www.youtube.com/watch?v=R3JEWQK5Drs
It's possible that the bug is unrelated to "Tour the Galaxy". I suspect the bug may be caused by turning while in slipstream.
(e) The auto-pilot sometimes stops too far away from the destination, so you have to move slightly in order to the complete objective.
(f) The stars and other objects, such as asteroids and stations, are too big and frequently get in the way. Several times, I found my path blocked by obstacles. I had to back up or fly around the obstacles before continuing. I suggest changing the Tour so that the player needs to pass through certain sectors rather than visit certain systems. This change would allow the player to plot a course away from the obstacles in sector space.
5. The huge stars frequently block the path to a system's entrance. The auto-pilot stops you right next to the star, which may put you out of range of the entrance. Whether you're in range or not largely depends on the direction from which you approach the system. If you approach from the side opposite the entrance, then you need to maneuver around the star to reach the entrance. This problem can be seen in the systems below. Each of these systems contains a patrol---the first two at planets and the third at an asteroid belt. In all three cases, the star blocks the path to the entrance if you approach the system from the wrong side.
Beytan System: http://i.imgur.com/Axik56K.jpg
Eirhess System: http://i.imgur.com/tOVLaPe.jpg
Toron System: http://i.imgur.com/nBII5tT.jpg
Stars can likewise block the path to social zones, such as Bajor and Defera.
Defera System: http://i.imgur.com/6BNAn1z.jpg
Bajor System: http://i.imgur.com/REDVSAB.jpg
In the last example, even though I clicked on Bajor, the auto-pilot stopped me next to the star right outside DS9.
6. The stars expand to a size that makes them look very close to your ship. But in most cases, a player's purpose in visiting a star system is to establish orbit around a planet or dock at a space station, not take close-range sensor readings of the system's star. For example, the destination of a player who visits the Sol System is likely Earth Spacedock or Starfleet Academy. But in sector space, Sol appears much larger than it would if viewed from Earth. The following screenshot was taken near Earth orbit in sector space:
Sol System: http://i.imgur.com/s8Mr7Qf.jpg
As you can see, the sun blocks most of my screen. Does the real sun look that big to you when you look up at the sky?
7. I saw a deep space encounter named "Deep Space Encounter: Intelligence Disaster" on the border between the Archanis Sector and the Gamma Eridon Sector. On a federation character, the deep space encounter kept flashing---appearing one moment and disappearing the next. On a KDF character, the deep space encounter did not flash, but there was no prompt to enter it.
8. The icons for systems, stations, and clusters look too big on the mini-map. I suspect that the icons are using a different scale from the rest of the mini-map. For example, when the mini-map is scaled to 50%, the icons are scaled to only 90%. These are not the exact percentages, but something similar must be happening. It's possible that the icons are using the scale for main map instead of the scale for the mini-map. The same problem appears on Holodeck, but it's more noticeable on Tribble because there are more systems. Take a look at the screenshots below. They were taken after zooming the mini-map to maximum size and then clicking the minus button 30 times.
Holodeck 03/02/2015: http://i.imgur.com/3u83Uns.jpg
Tribble 03/02/2015: http://i.imgur.com/nzzoyGd.png
9. When you fly near the border between quadrants, a window with your boff pops up asking if you would like to cross the border. Consider replacing the pop-up window with a simple button that says "Enter the XYZ Sector". I don't need a boff asking me whether I want to cross what should be a contiguous region of space.
10. The names of sector blocks in the mission text have been replaced with the names of quadrants. Since the quadrants are quite big, it would be more helpful to say something like "Go to the ABC System in the XYZ Sector of the Alpha Quadrant."
11. The transwarp list still refers to the "Tau Dewa Sector Block" and the "Delta Sector Block". Also, the order of the transwarp list on Tribble is different from the one on Holodeck.
Holodeck 03/09/2015: http://i.imgur.com/mFonOH5.png
Tribble 03/09/2015: http://i.imgur.com/COlzPrF.png
12. The "Beam Up" window at Starfleet Academy still refers to the "Sirius Sector Block". The "Beam Out" window at Klingon Academy still refers to the "Omega Leonis Sector Block". The "Beam Up" windows on Defera and the Defera Invasion Zone still refer to the "Deferi Sector Block". If you beam up from Defera or the Defera Invasion Zone to sector space, the system first sends you the Orellius Sector Block before sending you the Alpha Quadrant.
13. The beam-in and warp-in animations are broken, though the beam-out and warp-out animations still work. Also, the screen flashes when you beam down to Starfleet Academy or Klingon Academy: it looks as though you enter the map twice.
14. The visual effects are smaller now, but they still look wrong. Compare the screenshots below.
Borg engine plasma arcs (top): Holodeck, Tribble
Borg engine plasma arcs (rear): Holodeck, Tribble
Borg engine plasma trail: Holodeck, Tribble
Omega engine warp trail: Holodeck, Tribble
slipstream: Holodeck, Tribble
transwarp: Holodeck, Tribble
15. Before Legacy of Romulus, quantum slipstream drive would continue even after you cross into a new sector block. This was broken in Legacy of Romulus. Now, crossing the border between quadrants cancels quantum slipstream drive.
Tribble ticket #35,132: Changing zones cancels quantum slipstream
Quantum SlipStream Drive stops when going into Next Sector
16. The slipstream cooldown reduction for the Omega engine is calculated incorrectly. This bug is very old.
Holodeck ticket #1,722,948: Slipstream reduction for Omega engines calculated incorrectly
17. The tray forgets the position of the MACO 3-piece bonus Heavy Graviton Beam. If you swap the MACO engine for the Borg engine and then swap them back again, the tray does not place the icon for Heavy Graviton Beam back in its original position. On Holodeck, the tray remembers the position of Heavy Graviton Beam.
18. The commands "/showfps 1" and "/showCamPos 1" no longer work. They are broken in sector space, in system space, and on the ground.
19. Please consider bringing back Tribble Weekend in order to test the system under heavy load.
STOWiki admin.
Except some details:
Doffing: The cluster contacts often offer no assignements at all (For instance, clicking on the Rolor Nebula contact resulted in showing me an empty tab.).
Transwarps:
- The Tuffli and Suliban Cell miss almost all transwarps to clusters. Under the header 'Zenas Expanse', the three former Cardassian space clusters are shown. All other clusters seem to have transwarps missing.
- The transwarps gained by ranking up the Diplomacy/Marauding tracks don't show up reliably. One of my KDF characters was missing transwarps to Alpha Centauri and Regulus. A Federation character, on the other hand, seemed to receive all of the transwarps correctly.
Beam up:
- beaming up from Qo'nos system lead to my ship appearing in sector space above Boreth, not Qo'nos. Some 2 (or 4, was it?) light years away.
Overall, I'd like to stress the importance of fixing the camera distance trouble. On holodeck, you only have to set your desired camera distance upon beam up from a ground map (not always, but very often). On Tribble, due to the difference of ship sizes from system to sector, the camera distance also always resets when entering system space from sector (zooming in on your ship that becomes so much larger). In addition to that, the maximum camera distance in sector is still too small: larger ships (like the Kar'fi carrier or tuffli freighter) will still take up a large part of the screen at maximum distance, despite their scaling down.
And yes, I'm fast becoming far less of a fan of the huge stars. They're actually far more annoying than huge Scimitars blocking our paths on Holodeck. What would help? Obviously scaling them down somewhat. And also, making the auto travel move us always on top of the stars/planets/bases. That way, we'd no longer have to fly around them every time auto travel gets us right next to them.
Toi'Va, Ti'vath, Toivia, Ty'Vris, Tia Vex, Toi'Virth: Add Tier 6 KDF Carrier and Raider.
Tae'Va, T'Vaya, To'Var, Tevra, T'Vira, To'Vrak: Give us Asylums for Romulans.
Don't make ARC mandatory! Keep it optional only!
1 Nimbus System, in Star Trek V, The Romulan Ambassador says that the 3 governments agreed to jointly develop Nimbus III, Why would the Klingon Empire bother with this if the system lay between the Romulan Empire and the Federation??? quite simply put they wouldn't.
Surely a better place would be the Bottom part of Japori or Azure sectors.
2. Mutara Nebula I know the books and other stuff says it should be south of Klingon space but there's a huge problem. Why would the federation have a research facility in orbit of Regulus next to the Mutara Nebula if it is so far away from Federation space? They wouldn't the security risks would be too great, not to mention in Star Trek II the Enterprise gets there relatively quickly so it wouldn't be that far from Earth probably close to the Klingon Border but not where it has been put.
Better solutions Kassae Aldebran or Ba'aja Sectors.
3.Galorndon Core, it's supposed to be in the Neutral zone between the Federation and Romulan empires not on the far right hand edge of the map, it just seems too far over.
Surely moving it 1 or 2 sectors to the left might make more sense.
Just my suggestions, I don't know how others feel but there ya go.
Other than that I like the feel, yeah still a couple of walls but fewer issues loading. I can actually point and click and the go make a drink, come back an I'm there which is good
I'm loving the whole system enlargement as you approach, it gives you an appreciation or scale. Star Trek now looks BIG as it was meant to be :cool:
Douglas MacArthur - Quote on the dedication plaque of the U.S.S. Ranger NCC-97332-A Armitage class Fleet Heavy Strike Wing Escort.
Seen it. But I have herd people question how accurate it is. Don't know my self. The biggest question is why would the Klingons agree to jointly develope a planet so far away.
The inpression that I got was it was near all three borders.
Douglas MacArthur - Quote on the dedication plaque of the U.S.S. Ranger NCC-97332-A Armitage class Fleet Heavy Strike Wing Escort.
Who says it's far away? You're looking at a 2D map representing 3D space, Klingon space could very well border that area between the Romulan and Federation Neutral Zone. It's the same with dialogue said on DS9 where Romulan ships struck Cardassian outposts along the border with their space.
Commanding Officer: Captain Pyotr Ramonovich Amosov
Dedication Plaque: "Nil Intentatum Reliquit"
Holodeck 03/24/2015
http://i.imgur.com/vZb5nc0.jpg
http://i.imgur.com/kGd7iJe.jpg
http://i.imgur.com/vsb8uuO.jpg
http://i.imgur.com/mbSz5bd.jpg
Tribble 03/24/2015
http://i.imgur.com/EBT5wHF.jpg
http://i.imgur.com/7zQx83o.jpg
http://i.imgur.com/IaVo8L1.jpg
http://i.imgur.com/mes9xtG.jpg
We're playing a game with a 2D map, so unfortunately it needs to conform to how it is laid out, not only so it looks right but for the sake of common sense.
There's no rules that say it has to conform to a map that someone extrapolated, this person could have made a mistake clearly this is the case with the locations of some of these systems. STO devs have a chance to put them right afterall it's their game, I'm sure they'll get more flak from others when it goes live if things remain where that are, best to change them now and not have to move them later.
I've been over this numerous times already. No, Nimbus is not being moved.
The so called "Planet of Galactic Peace" was a poorly planned joint venture that none of the sides cared much about. We don't know the details about it's creation, but given that each faction used it as a dumping ground for their less savory citizenry, I think it's fair to assume that none of them really cared where it was. In fact, the Klingons may have been happy to have it farther away from them. Who knows.
What I do know, is that that's where Star Charts puts it, and that's what we're trying to follow here. We can (and apparently do) argue about it all day long, but there are much larger fish to fry.
Yeah, like Sol being incorrectly placed in the Beta quadrant!
:P
Just playing, I know it's always been there, all this bickering about planet placement is just very funny to me, lol.
Kind of makes you wonder why they are referred to as the Alpha Quadrant powers, when most of them reside in the Beta Quadrant, yet another weird thing in the Star Trek universe :P
Perhaps they should have employed someone to draw a map for them as they were making the series and stick everything on it correctly, I'm guessing during the 60's they had no budgedtor were stoned :P probably both.
I forgot where I read it (maybe io9.com or something), but someone looked over the episodes of TOS and realized that some of the "Away Team missions" were them just walking over to the sets of other shows happening near the filming stage. Aka, the Westerns, time travel, and the episodes about alternate earths.
So, budget was a bit "tight".
(UFP) Ragnar
It would make more sense to have all of the Doff missions in a quadrant available to select from in the doff UI rather than by sector as is now.
I can imagine this is a sticky design issue and there very well my be some drawbacks to viewing and selecting from such a large list but the current theory of trying to keep the doff missions separated by sector really aren't working fluidly for me (an others I assume). The recent changes to the doff UI - allowing a streamlined view of doff missions - could overcome that burden.
Is it possible to at least offer a one week test of this change to see how viable it is? It's a gamble for sure but if doffing rolls out the way it is now I guarantee you will find yourself making changes to its function soon enough. The logic which is being applied now makes sense in a sector isolated map design since I will always know what sector I'm in and cannot move between sectors without manual involvement. With a more open map sectioned by quadrant that design theory loses its relevance.
It's obvious your are working under the requirement of showing a manageable list of missions to the player by moving a majority of the missions under first officer recommendations to no clutter the main screen but this requirement is forcing bad design and a lower QoL in my opinion (for one it muddles which missions are sector specific and which ones are first officer recommendations specific - one group is static while the other is not). I'm not afraid of a large list, especially with the redesign of the doff UI it's not unmanageable.
One way could be removing some doff missions. I am not referring to any of the chained missions, personal missions or first officer recommendations, or the special higher quality sector only missions but to the list of available standard common missions that offer no additional award other than basic mats/dil/xp/commendation. If you indeed move to show all missions for a given quadrant there is only a certain amount of missions one captain can assign at a time. This way we leave missions where they are now with the personal and first officer assignments screens not seeing an increase and with the main ui screen showing an increase in listed missions by something like 100-125% (so double the size of the current list or a little more). So instead of seeing 3-5 science missions awarding mats it might now be 10-15 (of course you would need to adjust the numbers to accommodate those who assign more than 20 missions). That should provide a much more manageable list than providing all of the current doff missions available in an entire quadrant. Again, as long as you don't remove the special doff missions and only reduce numbers in the common non chained missions no one should miss anything. You won't be able to assign all of the missions anyway.
Thanks for the response. Did not mean to make you repeat yourself. I looked but did not find a Dev response about Nimbus.
Douglas MacArthur - Quote on the dedication plaque of the U.S.S. Ranger NCC-97332-A Armitage class Fleet Heavy Strike Wing Escort.
It's not as random as it sounds. It's a matter of studio. TOS was produced by Desilu. Desilu (owned by Lucille Ball, yes, Lucy, from I love Lucy) owned the sets for the Andy Griffith show, so it was simply a matter of scheduling their use.
My character Tsin'xing
repost of a post i made elsewhere...
EDIT: took me FOREVER to find that post! we have DevTracker. what do we need to do to make a MeTracker?
Well didn't most of the referencing take place during DS9? I wouldn't be surprised for that show if they went with "Alpha" over "Beta" just for the sake of a better sounding line (which you could try to justify by the fact that the FED is spread on through part of the AQ, ignoring for the moment the ROM and KDF....)
Also, one bit of Sector revamp feedback. Max zoom (towards ship) causes the player ship (or to be more specific if its not a universal problem, my Ma'Tha raptor) to disappear from some angles. Shuttles have had the same problem for quite some time (and it is quite annoying for those that like to appreciate details).
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
No worries. I know there's too much to sift through. It's just funny how often the same things come up.