You can do that too with hudshift configuration for the HUD, and for the Xhair, easy to hide it 🙂

I think wplatform may fire cd only as ship but not as object

The jumpholes are the only things we’ve added into the mod at this point. Eagle Utopia has had them for years but I don’t know what they did about the paths.

EU had added jumpholes to added clone systems. The JHs were placed well out of the ‘normal’ locations an unmodded player would be expected to fly for this reason.

Other than an unmodded player crashing when coming within 5k of one of these JHs while it was being used, they’ve had no ill effects. In fact, as long as no one was using the JHs, they could fly right up to them with no CTDs. The moment the hole was activated however, they would crash.

cheers for that guys, time for testing 😄

Yup. There is sort of a ‘middle-man’ approach to this.

If you open up ‘select_equip.ini’ you will find this section in it:

[InternalFX] nickname = trading_outpost use_sound = rumble_solar_small

Which is what the equip entry references in your loadouts file. This then points it again to the sound in ‘sounds.ini’, and from there the sound file itself gets played.

~Fury

[ShipClass] nickname = BOMBERS member = bomber member = heavy_bomber

F!R wrote:
Give it a base 2 go
and
sett all (maybe define only 1) docking points to use moor_medium like

docking_sphere = moor_medium, HpDockMountA, 15.000000

And no player will be able 2 dock that base.

😉

Eeek, nooooooooooo……

Erm if the base type your using has hpdockmounta modeled as a berth, then your suggestion will just end up having trasnsports trying to fly into and out of the hanger…

; docking_sphere = berth, HpDockMountA, 4.500000, Sc_open dock1 ; docking_sphere = berth, HpDockMountB, 4.500000, Sc_open dock2 docking_sphere = moor_medium, HpDockMountC, 5.000000 docking_sphere = moor_medium, HpDockMountD, 5.000000 docking_sphere = moor_medium, HpDockMountE, 5.000000 docking_sphere = moor_large, HpDockMountF, 5.000000

Just comment out the dock types you dont want the base to use, but dont change the letters unless you rehardpoint the mesh.

Also be aware that if a player has a ship with a docking property that isn’t ‘berth’ they could still land, and since all player launches default to dockmount A, they endup trying to moor (get stuck unless they hit the escape key before the docking cutscene ends) and then launching their transport/capship from the fighter bay, it also means that npc fighters can launch from the base, but cant dock again… so depending on how you set up your encounter types and pop zone, you might end up with a bunch if fighters circling, waiting to land in order to despawn but unable to do so, and basically filling up the pop zones population cap so there is no room for ‘normal’ traffic, just because somebody shot up a base a bit, while other uninvolved players were present to prevent npc auto despawns.

@Vital:

Get yourself “trying to understand encounters” tutorial by Buck Danny. It has to be in tutorial downloads section.

YUP - that’s the one i was talking about.

Doesn’t look like a standard FLServer error message to me, more like one from a server-hooking addon (FLAC perhaps?).

Cheers FF your an absolute star, The values in the explosions.ini were set miles too low and also the energy_damage line was missing so a bit of tweaking and hey presto they work again 😄

that’d be about right.

oh well guess ill just edit the ale of the working thruster to make some different coloured/shaped ones 😉

yw

you may even try the gf_flakcannon (weapons_ale.ini) without ALE editing it already looks great… 😉

PS: And never forget, realistic look isn’t the most important, just make a beautiful effect which reminds players a smoke grenade. If you want to make something cool: 1. make sg beautiful 2. modify it to remind us a realistic effect. 3. Make sure it looks nice from close and far away as well. 4. optimize (performance)

oh well guess it will stay as it is then 😞

NOD32 isnt detecting anything…

**I recognise that error list from my error checker, what it means is the number on the left is the number of exhaust nozzles in the shiparch entry and the second number is how many that is in the actual CMP file.

I added the extra engines on all of those ships, the only one I noticed it having an effect on was the Liberty Battleship. It created several smaller flames mixed in with the big flame. You can of course change the flame FX to what you want it to be.

And no, you do not have to add them but it will get rid of the errors. That feature was added since I have over 450 ships I didn’t want to have to hunt down all of them that had missing flames.

Almost forgot, I saw several with more exhausts than the CMP has, you do need to fix those. You will get random crashes if you don’t.**