|Anatomy of a Starship
||evilbobthebob - June 22, 2014
Probably the best way to introduce the new space combat mechanics is to take a detailed look at our new (WIP) infobox layout. You may recognise many of the elements from the revamped land combat; many of the elements are also new. I'll go through each in the order they appear using the classic example of the Imperial II-class Star Destroyer. Please note that all values shown are WIP.
Tactical Population Cost
This is a new number based on the total volume of the hull (or hulls in the case of a starfighter squadron). It is balanced around the idea that an Executor-class Super Star Destroyer consists of 400 population points, the maximum available space population. For carriers, it also includes the volume of all the starfighter squadrons as in the case of the Imperial II. This means that you can field 5 Imperial II-class and their entire complements at one time. These values are currently in the process of testing and tweaking, and the exact values may be different in the released version.
All the starship icons have been brought into lineusing uniform lighting and rendering settings to create a better quality icon set.
As usual, we retain the full names of all ships, including their upgrade version.
From Starfighter through to Dreadnaught, a starship's class helps shape its maneuverability and sensor range statistics. It also determines which shipyard type is needed to construct it.
With the new version, we have many greatly improved autofire scripts for ship special abilities, so we feel comfortable including more than the two accessible from the GUI. In most cases, the tractor beam will be the hidden, autofired ability, and it will usually target whatever the ship has been told to attack. Note here the Imperial II has a Tractor Beam, Emergency Thrusters (power to engines ability) and Blast. Blast is a new ability we have added to many main-line combat ships. It moves the firepower of the main battery (in this case, the octuple turbolasers and turboions) up a notch, so that has increased range and firepower.
We have always included manufacturer bonuses on various appropriate planets such as Kuat. Now you can see exactly which ships will benefit, with the inclusion of the Manufacturer in the infobox.
This is the base hull cost, not including complement (which is included in the final cost at a 50% discount). Costs have been modified across the board to provide a more challenging economic planning experience.
This is the base hull construction time, measured in galactic time. For the Imperial II, this is 15 weeks. Note that building over a world with appropriate shipyard bonuses, or by building more of the same class of shipyard, this time can be dramatically reduced.
Width x length x height, in meters, the basic size of the hull.
The total volume of the hull in cubic meters, often using exponential notation. Here for example, the Imperial II is 121 million cubic meters in volume. This statistic informs hitpoint calculations and has a great effect on the likelihood for a ship to be hit by enemy fire.
With the change to the new space combat mechanics, we have moved towards a more "realistic" approach. While ships still have a capped top speed, it is directly proportional to their acceleration. This is measured in terms of G-force, the acceleration experienced by a being on the surface of a planet with standard gravity, roughly 10 m/s2.
This statistic is the turning speed of the starship, measured in degrees per second. It is primarily class-based.
The class of the hyperdrive in the starship (if any), which determines its ability to travel across the galaxy in hyperspace. The smaller the better!
Here is one of the new statistics. Shielding is now measured in Shield Points (SP) and has an absorption percentage shown after it. This is the amount of damage the shield can absorb from a single shot before it takes SP damage. So for example, a turbolaser shot hitting the Imperial II shield with a damage of 96 will do around 58 points of shield damage.
Hull has also changed a great deal. It is now measured in Hull Points (HP), like that of land combat. This value is primarily volume-based. Following the HP is the armour value and type. The Imperial II has 32 Vehicle armour. This means that it absorbs 32 damage from any incoming shot before the hull itself is damaged. For example, the same 96 damage turbolaser will do 64 points of hull damage on impact.
This statistic shows the maximum and minimum ranges of the weapon systems on the ship, followed by its line of sight range. All values are in meters. In this case, the longest range weapons are the octuple turbolasers, while the shortest are the individual turbolaser cannons.
We have greatly condensed the weapons display into a shorthand that provides much more information. We have done away with "light", "heavy" and so on, instead simply telling you the weapon type, their number, and their damage output. So, here the Imperial II has 6 octuple turbolasers with 240 damage per bolt, 2 octuple turboions with 240 damage per bolt, 2 triple turbolasers with 144 damage per bolt, and so on. Note that ion weapons do 200% damage to shields, but cannot damage anything except Droid armour. The number of tractor beams is also noted, which adjusts the cooldown of the tractor beam ability.
I hope this little snippet has provided some insight to the changes we've been making over the past 18 months. If you have any questions, I will endeavour to answer below, however note that I did not implement these changes myself.
|News. Now that's a name I haven't heard in a long time...
||evilbobthebob - June 17, 2014
Hello Phoenix Rising fans.
First off, I'd like to apologise for the extremely long time between news posts. If this was the only way you kept up with the mod, I can forgive you for thinking we'd ceased development. Those of you who read more of the forums see the team members making comments from time to time, and we made a call for alpha and beta testers for the latest version over the past year. Still, this doesn't make up for the silence we've sustained up to now.
I'd like to change that myself, primarily because I finally have some free time and partly because our team leader and the prime driver of the mod, Phoenix Rising, is without a computer capable of doing modding right now. This isn't particular cause for alarm, because the current build of the mod is very feature-complete. However, there still remain areas that need polish and improvement.
So what have we been doing for the past two years? Our initial plan for the next version of the mod was primarily based on integrating the information provided by the release of The Essential Atlas. As software project tend to do, we experienced some rather strong feature creep, and as one thing led to another, we realised we had a version of the mod that is no longer a mere incremental update. In fact, we have:
- Made numerous changes to improve performance
- Remade and rebalanced the hero system
- Rebalanced tech trees
- Galactic Mode
- Brought our galactic maps in line with The Essential Atlas
- Added new planets
- Entirely rebalanced and remade our core sandbox campaigns (still a work-in-progress)
- Created a new planetary bonus system
- Created a new hyperspace system
- Rebalanced freighters, including the addition of light transports
- Improved the display of research
- Improved land combat
- Begun the process of adding infantry weapon models
- New units
- Improved weather system
- Added many new maps in land and space
- Entirely revamped space combat to be in line with land combat:
- New armour, health and shield system
- New weapon balancing and types
- Better display of unit statistics
- New units
- Increase in map size to accommodate the changes
Many of these changes, especially those based around planets and maps, have already been mentioned in prior news posts. Check those for more information on those specific topics. As for the rest, I hope I can bring you more news posts in the near future providing examples and details. In the mean time, I'm happy to answer questions you may have here on the forums.
|"Commenor must be some major-league trading planet"
||evilbobthebob - December 10, 2012
|Sited in the Colonies, Commenor is a bustling, arid trade world. Its surface is covered with starports and landing strips for the tonnes of cargo that arrives and leaves, bound for the Core and the Rim. The planet swiftly became independent after the Battle of Endor, but its strategic location means that it's unlikely to stay that way for long.|
From an initially defensible landing zone, attackers must choose if they want to push up a ramp onto the upper landing strip, or move out onto the open ground below the small clusters of mismatched city buildings.
Commenor's varied architecture is the result of its trading heritage; a melting pot of many different races and influences. Of course, both the Empire and New Republic would like to make their mark on the planet...
Whoever takes control of this world, it will certainly assure them dominance across the Trellen Trade Route and easy access to the Slice.
|The Road To Coruscant
||Phoenix Rising - December 10, 2012
|Two-and-a-half years after the Empire was sundered and beaten at Endor, the war against its successors has stagnated. The New Republic has failed to gain more than a foothold in the Core and member worlds are beginning to doubt its legitimacy as a galactic government. The risk of this fragile coalition unraveling is too great, thus Supreme Commander Ackbar has drafted a campaign to thrust into the fortified Core and seize the galactic capital. This is the Road to Coruscant.|
Director Isard acquired the throne a little more than a year ago; however, it took the sacrifice of Brentaal to the New Republic in a complicated coup to put her there. From Brentaal, there are two paths to Coruscant: through Anaxes, or through Borleias. With Admiral Ragab locked in a standoff with Commandant Wermis on the Brentaal-Anaxes front, any movement on Borleias would require reinforcements. The answer came in the form of resurrecting the all-hero Rogue Squadron.
A secret training base was established on Folor, with General Salm in command. There, six new starfighter squadrons will be forged, including Commander Antilles' Rogue Squadron. The reformed Rogues are made up of seasoned pilots with a variety of leadership skills that, in most cases, also happen to hail from key worlds. They are equal parts elite unit and poster subject.
The plan is to temper the Rogues with a series of active duty exercises against Imperial forces in the relatively quiet Rachuk sector before commencing the main offensive. Rear Admiral Devlia coordinates the sector's Force Escort from the capital of Vladet.
When the time comes, the Rogues will rendezvous with the New Republic Special Forces units staging on Noquivzor, along with whatever Fleet elements Ragab can spare. This group will move on Borleias under General Kre'fey. A word of warning: Borleias may look mundane, but the name has been linked to General Derricote, the eccentric bioweapons engineer.
In addition, Isard has a noted obsession with Rogue Squadron, who had previously helped foil several of her schemes. If the Rogues were ever annihilated to the last pilot, not only would it be a personal victory for her, but also an insurmountable propaganda nightmare for the New Republic.
A more conventional victory for the Empire would occur if loyalist forces were able to reconnect the Perlemian, pushing the New Republic from Brentaal, Ralltiir, and, finally, into the Colonies. Such a position would all but spell an end to the New Republic presence in the Core - and any hope of claiming the capital - for the foreseeable future.
Coruscant, of course, is the only prize for the New Republic. Controlling the Palace would secure the Provisional Council's authority, while the Rotunda would allow a senate to convene for the first time in years. The expected battle will be anything but easy: some of the best units in the Empire are garrisoned here. That's why Rogue Squadron will lead the way.
|Recopia: Base of the New Republic Defense Fleet
||evilbobthebob - December 7, 2012
|Situated between the Corellian Run and the Hydian Way, the planet of Recopia is ideally located to strike the other planets of the Core Worlds. This strategic position, and the relative anonymity it provides, made it the base of operations for the New Republic Defense Fleet in the period immediately after the Battle of Endor.|
The reason this planet is ignored by the rest of the Core is its geography: sulphurous seas, poisonous fog and a lack of natural resources meant that a mere 200 million sentients call it home. They live scattered across the kilometre-high plateau islands that are dotted across the oceans, connected by bridges or airspeeder.
Due to the sizes of the islands, vehicles cannot be deployed to the surface. Instead, airspeeders and infantry are required of any garrison or attacking force that wishes to take the planet. Any structure on the planet must be carefully chosen to make best use of the limited space available.
The bridges provide choke points and defensible locations, while the small islands end up filled with skirmishing and air-to-air combat amid the lashing rain.
|Our Best Case Yet For Mod Of The Year
||Phoenix Rising - December 3, 2012
|2012 has been a transformative year for us. Version 1.2 premiered in March and we've been anything but idle since. After wrestling the engine for years over certain features, we've finally reached a point where our design is beginning to fall into place. There are plenty of updates to reveal over the next couple of weeks, but for now, please help get us into the Top 100 by voting in Mod DB's annual contest. Just click on the wrench and trophy image to visit our page, then click again on the "Vote For This Mod" button in green.|
As you may know, Nertea was busy publishing his own mod for Battle for Middle-earth in between modeling our vehicles. Kindly consider voting for The Dwarf Holds, which also had a major release this year.
|Traveling Through Hyperspace Ain't Like Dusting Crops
||Phoenix Rising - November 29, 2012
|Research has always been an integral part of our development process. No demand has been more of a challenge in that regard than our need to place each planet at a definite galactic location for strategy mode.|
When I began the process in the alpha phase of v1.0, there were maybe four official maps available that held any degree of accuracy; all were clearly related by the reference angle. Beyond that were hundreds of raw sources netting thousands of remarks about regional or relative location. Had that been the end of it, my task would have been nearly impossible.
Fortunately, an adolescent Wookieepedia was available to help cut through much of the clutter. And then I found this fellow called Modi, who had translated the askew maps onto a Cartesian plane, allowing me to derive coordinates that could be fed to the engine. It was the Internet equivalent of striking gold - a starting point. Later, JustinGann expanded on Modi's work to include speculative placements, which afforded me a second opinion. The end result was an independent interpretation of the galaxy unique to Phoenix Rising.
It took the single most important update to the canon to void all that effort - for the better. Midway through v1.2, The Essential Atlas hit bookshelves. Every star system that had ever been mentioned was now bound to a region of space 1/576th the area of the galaxy. A great many were placed with certainty. The unprecedented accuracy of the atlas created a dilemma though, as several campaigns had already been finalized for the release. Rather than scrapping them and starting over, we chose to forge on knowing that v1.2's astrography would be flawed. I am pleased to report that the next version will be anything but.
TEA contains dozens of maps, each with its own scale and set of planets. My first step in replotting the galaxy was to composite them at a scale of 1 pixel = 10 lightyears to create a supermap. The digital Mid Rim sector map served as the foundation, since it had no loss of precision from scanning and little artifacting.
With that done, the actual measuring was trivial. The results were better than I ever could have expected: the first planetary coordinates for Abregado-rae came in identical to those already in use. They were not alone. Although I had corrected our most glaring differences - generally those with no frame of reference or cases where TEA chose to reject Rebellion placements while I did not - when prudent in v1.2, our interpretation really held up to intense scrutiny. Only Spuma, which Children of the Jedi had confused with Protazk, and Orinackra were completely off.
The present and final representation of the galaxy is 20% larger than v1.2 and approximately 92 times the area of vanilla. That should be enough space to prevent planetary overlap in all future cases. Several worlds always have to be manually relocated regardless of scale, but not so much as to be a distraction.
As profound as it is to finally have set astrography, a different facet of TEA had an even greater impact on strategic gameplay. The once-sporadic and eclectic collection of hyperlanes was replaced with a vibrant trade network.
In v1.2, we had two kinds of routes: "the Big Five" and "other". There are now four classifications, the most I could objectively derive from official maps. These can be thought of colloquially as "super", "major", "minor", and "trace" routes. Their benefits are scaled linearly, so while traces provide only meager income, they are much quicker than using a navicomputer to punch though an unstable course, as is the case with non-route connections. Obviously not every system can be linked via hyperlane, so we have tried to balance between using intersections and minimizing campaign planet counts.
These connections are now critical to military operations in the Galaxy Far, Far Away. In the next release, fleets will not be able to travel from a planet unless there is an explicit line - we have eliminated proximity jumps. No longer can an invasion bypass Anaxes on the way to Coruscant, players need not guess where to attack and defend, and the AI has fewer perceptions to crunch when executing plans. This is arguably the single best change that has ever happened to strategy mode.
When FoC was released, I never imagined we would be able to deduce coordinates for every star system. If our trials and errors played even a miniscule part in affecting that change, then it was all worth it.
|The Revolution Is Here: Phoenix Rising v1.2!
||Phoenix Rising - March 25, 2012
|The culmination of 39 months of work. Hope you enjoy it! We look forward to your feedback.|
If you've previously installed other mods, make sure they haven't put any files in XML or Scripts folders in EaW\GameData\Data and FoC\Data. PR v1.2 is fully compatible with other mods; it just looks like certain mods are incompatible with us!
If you've previously installed the LucasArts 64-bit OS, 2+ GB RAM patch found here, you must apply this compatibility fix after running the PR v1.2 installer. The LA patch alters the original files for FoC v1.1, creating an instability in mods with custom AI. PR v1.2 allows 2+ GB RAM natively.
||This level is not made, distributed, or supported by LucasArts, a division of Lucasfilm Entertainment Company Ltd. LucasArts, the LucasArts logo, STAR WARS and related properties are trademarks in the United States and/or in other countries of Lucasfilm Ltd. and/or its affiliates. All other content copyright Phoenix Rising Team 2006-2012.