Thanks guys. Ill look at the hd version. I just joined Galactic Community Discord. Apparently my name has been used, so Chop_420 is myself. I’'m going to look into everyone’s suggestions.

You need to edit the NewCharacter.ini in Data, Characters and change the info in there

[Faction]
nickname = new_player
rep_group = co_ic_grp
base = Li01_01_Base
Package = ge_fighter
Pilot = trent

thanks for doing that, I’ve been a bit busy with rl stuff.

Alucard if you need any more just ask on the Discord and I’ll post them up for you

I did my tools for 3ds Max because I’m much more familiar with it. Until someone makes equivalent for Blender, but that probably won’t be me. Maxlancer is open source and there are lots of comments to help figure out how Freelancer formats are put together for anyone willing to try.

Piper’s plugins for Milkshape may have been the latest of the bunch but they too haven’t been updated in a very long time, and like tools from that era they have plenty bugs, mostly from insufficient information about data structures in formats.

Large .sur size is indicative of a bad export: some tools “break” concave meshes into double-sided triangle hull per mesh face. Accumulative BVH offset drift bug in obj2sur only exacerbates the issue and results in unstable hitbox. Freelancer collision physics are fine as long as you feed it correctly pre-calculated and well optimized data.

Sure thing!

EQUIPMENT\select_equip.ini

[AttachedFX] nickname = fx_sun_ale particles = Sun_ale_eft

FX\SPACE\space_ale.ini:

[VisEffect] nickname = Sun_ale alchemy = fx\space\Sun.ale ; effect_crc = 3967695840 CRC is case sensitive! effect_crc = 103825916 textures = fx\smoke.txm textures = fx\missleeffect.txm

FX\effects.ini

[Effect] nickname = Sun_ale_eft effect_type = EFT_EQUIP_ATTACHED_INSANELY_LARGE vis_effect = Sun_ale

SOLAR\loadouts.ini

[Loadout] nickname = magmaeater_load archetype = magmaeater equip = scalar_howitzer, HpWeapon01 (...) equip = fx_sun_ale, HpFx01

UNIVERSE\SYSTEMS\Iw07\iw07.ini

[Object] nickname = Iw07_magmaeater (...) pos = 25050, -4300, 13250 Archetype = magmaeater loadout = magmaeater_load

If you want to, you can add my 40 custom ales to your package.
They are all finished and open source

Looks awesome, keep up the good work.

You might want to hop over to the model showcase and pick up the new equipment base and textures I made. Feel free to grab the models I have there to see how I manage things. Or just post some pics of your own ships!

Alucard wrote:
Feel free to use, just credit me thanks

https://www.dropbox.com/s/tkcfu3ghlzp0xbm/spacestation textures.rar?dl=0

404 error…

Nah, it’s a special node type, just like Nebula in starspheres. They have unique properties.

It seems that P1p3rs Exporter is automatically reducing a single part object to a 3db file. The filename doesn’t change anything.

In a normal CMP you always have the node <partname>_lod1 and inside of this one comes MultiLevel or VMeshPart.
In a 3db’s file structure, MultiLevel or VMeshPart comes directly, without any parent node.

His exporter doesn’t make single part CMP files as the old exporters did. So you have to handle all your single part ships/objects as 3db file. There is no difference except you have to use the NONE option in the sur exporter and Hard CMP won’t show you the Sur (but it will work, trust me).</partname>

I stand corrected. 🙂 I’ll check it out, thanks mate.

Cool, got it to do what I wanted, but now have to figure angles and why the rest of the cmp isn’t showing up. Thanks mates.

Ok mate. As I don’t know C++, I thought I ask. 😄

Ok, using the 1.1 patch and 1.6 hook, still nothing. Is there a special number I should put it at? I thought 0.9 is max that you can get.

Yeah I saw after posting, oops. 🔨

I think its only client side adjustment. Latest release I think as by default has automated hudshift adjustment, but if doesnt work (like at me where hud elements stay in middle - they not touch edges of screen), option to set ur preferred is left. It also needs fl restart so that in game set resolution take effect.
This is all without me using JFLP server/client side.

If you do this on effects that use the beam functionality (effect defined in beam_effects.ini) and if the beam gets destroyed (i.e. hits something) before the corresponding light effect completes, Freelancer will crash. We kinda solved this by some hacky workarounds in Freeworlds but it’s still under testing.

Here you go: http://digitalbrilliance.com/modules.php?name=Forums&file=viewtopic&printertopic=1&t=268&start=0&postdays=0&postorder=asc&vote=viewresult

yep, sorry ^^

Try this, seemed to generate it fine for me