(03-06-2015, 08:48 PM)Toris James Gray Wrote: There's a very problematic technerf, which disallow Gallic Junkers to fly Junker stuff efficiently. Why? While they have (on tech tree) full 100% on Junker stuff, the Sirian Engines gives them 75% core. Mounting Gallic Engine onto Sirian ship will give ship 10% core.
Which Junker ship(s) are affected?
GJ Salvager and Collector work fine with CNORx engines (the GRN ones).
I haven't tried any of the other Gallic engines, but both ships had a 75% nerf with the stock engines.
(03-06-2015, 08:48 PM)Toris James Gray Wrote: There's a very problematic technerf, which disallow Gallic Junkers to fly Junker stuff efficiently. Why? While they have (on tech tree) full 100% on Junker stuff, the Sirian Engines gives them 75% core. Mounting Gallic Engine onto Sirian ship will give ship 10% core.
Which Junker ship(s) are affected?
GJ Salvager and Collector work fine with CNORx engines (the GRN ones).
I haven't tried any of the other Gallic engines, but both ships had a 75% nerf with the stock engines.
They should remove GJ nerf onto Sirian Engines, since it makes little to no sense, due to the background lore of Junkers and same ancestry for both SJ and GJ groups.
CNORx will work? That's new for me and I need to check it, since all I knew was that Gallic Engines cannot be mounted onto Sirian (so Junker as well) stuff, what would give 10%. Didn't know that to be honest.
Making a giant list of Gallia Infocard typos and/or inconsistencies.
Maine:
-Chateau-Gontier Freeport has 0 Population (Intentional?).
Picardy:
-Avre Asteroid Field makes mention of a non-existent JH to Burgundy.
Ile-de-France:
-Oise Asteroid Field is listed in two separate, distinct fields with the same infocard.
-Senart Debris Field mentions orbiting a planet (Creteil) that is is far away from.
Burgundy:
-Montbard Base lists that it is located within the Morvan Asteroid Field; it is actually located in the Autun Nebula.
-The Morvan Asteroid Field mentions high Brigand presence when there is a Corse base within.
-Macon Base states that it is within the Voiron asteroid Field; it is actually located in the Nievre Asteroid Field.
Champagne:
-Aube and Ardennes Asteroid Fields appear to have their infocards reversed.
Lorraine:
-Longwy and Le Thillot Asteroid Fields appear to have their infocards reversed.
-Toul Nebula mentions high Maquis presence when there is an Outcast base within.
Lyonnais:
-Rhone Nebula mentions four stars in its description; there are 2 within Lyonnais.
Berry:
-Cher Ice Asteroid Field mentions a high Maquis presence when there is a Brigand base within; it also mentions a non-existent JH to Orleanais.
-Indre Asteroid Field mentions a high Brigand presence when there is a Maquis base within.
-Aubigny Asteroid Field mentions a non-existent JG to Dauphine, since moved to the Creuse Nebula in the same system.
Orleanais:
-Loire Ice Asteroid Field mentions non-existent Lyonnais and Dauphine JHs, and it mentions the Nere Nebula being inside the field incorrectly.
-Mainvilliers (Moon) incorrectly mentions being within the Loire Ice Asteroid Field.
-Beuvron Debris Field incorrectly mentions being within the Loire Ice Asteroid Field.
Flew from Texas via Kepler to Kusari, on the way back ( same path : )
11/03/2015 : about 7:27 SMT - Discovery 4.88.1.00.01
Jump Li04_to_LI13_hole is missing a valid goto= in file Universe\systems\Li04\Li04.ini
Jump LI13_to_Li04_hole is missing a valid goto= in file Universe\systems\LI13\LI13.ini
Disco froze, I restarted via Launcher,
ship was placed at the Kepler side of the Kepler <> Shikoku JG without any more issues
(03-11-2015, 08:32 AM)FynnMcScrap Wrote: Flew from Texas via Kepler to Kusari, on the way back ( same path : )
11/03/2015 : about 7:27 SMT - Discovery 4.88.1.00.01
Jump Li04_to_LI13_hole is missing a valid goto= in file Universe\systems\Li04\Li04.ini
Jump LI13_to_Li04_hole is missing a valid goto= in file Universe\systems\LI13\LI13.ini
Disco froze, I restarted via Launcher,
ship was placed at the Kepler side of the Kepler <> Shikoku JG without any more issues
(03-11-2015, 08:57 AM)Lythrilux Wrote: When I opened FL comp I had an error message detailing this, I didn't think much of it though.
Quote:11/03/2015 - Discovery 4.88.1.00.01
- Tentative fix for missions. The Texas-Minnesota jumphole has been nuked as such.
- Added a duplicate Criminal commodity for BHG.
So its not a report on the jump gate I just passed ( and I probably just Disco´ed at because of net issues ) but the Minnesota JH that is reported there ?
ok, nice to know.
No worries, no other issues encountered
In the Minnesota system the Texas Jump hole displays the name: "Jump Hole" instead of "Texas Jump Hole", i attempted to jump through it twice and got stuck in the event horizon on both occasions. Everything else was normal on the server at the time.
(03-11-2015, 11:18 AM)Vycos Wrote: In the Minnesota system the Texas Jump hole displays the name: "Jump Hole" instead of "Texas Jump Hole", i attempted to jump through it twice and got stuck in the event horizon on both occasions. Everything else was normal on the server at the time.
Alley Wrote:11/03/2015 - Discovery 4.88.1.00.01
- Tentative fix for missions. The Texas-Minnesota jumphole has been nuked as such.
- Added a duplicate Criminal commodity for BHG.