Invisible Gun Fire from Mission Solars
-
Morning, I took a bit of time this morning, to review all the stuff on LR and do a little testing this morning, and this is probably stuff that a lot of you already know…
I created a new mission solar, copied from Space_Freeport01 and added a number of additional turrets to it. I find the vanilla ones difficult to test with as there aren’t many and they don’t cover every angle around the base.
I defined the new base in solararch.ini created a new loadout in solar\loadouts.ini and then put new solar in killablesolars.ini
I upped the difficulty of the 4 solars pilots in pilots population.
These are the results:
OpenSP
solar_type = Defensive_Solar - will fire both projectiles (missiles/torps) and turrets, and the turret/gun fire is visible.
solar_type = Big_Solar - will only fire projectiles. Guns don’t fire.
Multiplayer
solar_type = Defensive_Solar - will fire both projectiles and turrets, turret/gunfire is invisible, but I know it’s there because it’s damaging my shields (and there’s nothing else on my scanner).
solar_type = Big_Solar - will fire projectiles and turrets, turret/gunfire is invisible (shield damage).Other things of note:
the weapons turrets are never rendered on the base (or wep platform).
the “freeport” base would often damage itself from the invisible gunfire.
archdb errors in FLServer where it couldn’t find the new base or weapons platforms (when they spawned) I believe a bunch of guys on the old LR managed to circumnavigate this by adding a duplicate entry in shiparch.ini.
So it’s riddled with bugs even in the vanilla code.
@Helloween I did try those alternative const_effects, but as I suspected, they didn’t show up. Flak is no problem as I create FLAK from projectiles and have done in the past.
Adoxa I know you’re a busy man but is there anything in here you could work with?
In particular it’d be very nice to get rid of the archdb errors that pop up, so at least we could get them launching Flak projectiles without having to create duplicate entries in Shiparch.ini?Cheers,
Rik -
I believe he is referring to these errors:
ERROR: ArchDB::Get(2837983242) failed = Large Space Station (rm_space_freeport01) 0xA928300A
ERROR: ArchDB::Get(3098097218) failed = Defense Network (wplatform) 0xB8A93642
ERROR: ArchDB::Get(2547721671) failed = Observation Post (rm_space_police01) 0x97DB25C7
ERROR: ArchDB::Get(2686061189) failed = Outpost (rm_space_mining01) 0xA01A0A85
ERROR: ArchDB::Get(3064446595) failed = Defense Network (small_wplatform) 0xB6A7BE83There are more, every solar that can be spawned in a random mission. These show RED in the console and show in the error log even though they are not errors. The objects spawn in space and work as they should. I believe the only reason they show is because they are ‘virtual’ and don’t exist in the system ini file.
-
He is! Thanks Dwn.
-
common.dll 0995B6 FF10->9090 = disable "ArchDB::Get" random mission spew warning PART 1 ~adoxa common.dll 0995FC FF12->9090 = disable "ArchDB::Get" random mission spew warning PART 2 ~adoxa ```What's actually happening is GetArchMaxHitPts tests for a ship archetype first, displays the message when it doesn't find it, then tests for the solar. Part 1 disables the ship message (which is really all that's required); part 2 disables failing to find a solar, so the message only shows up when it also fails to find equipment. As for making it visible, that will have to wait… -
Change the Solar’s type to weapons platform 's the only way.
AND, if you cannot see fires even it’s already weapons platforms, you might be want to use missile instead those guns, flak, you know, set missile to rocket, so it will has gun’s behavior. Just remember set the missile’s auto_turret = true.
-
Great, thanks Adoxa! Good to see you back around!
