@adoxa: Just tested on my local copy, works, thanks dude.

Bear in mind that there’s some “special” ids names to handle, too. Specifically, look at how the faction ids names are handled, as well as zone names (for nebulae and asteroid fields). If they’re not in the right place with the right naming patterns, they won’t show up in certain circumstances, such as mission descriptions.

I’m sure I’m forgetting a few other special cases.

Well, that was a rather stupid error on my part. The only planets that were messed up were a couple older ones that I forgot to fix after Adoxa told me how. Embarrasing, but it happens.

Not sure what you mean. You can see your real speed by using FL Hack (btw, the plugin will override Hack’s lane speed) or patching Freelancer.exe directly:

freelancer.exe 0D597A 999i = speed over which “–-” is displayed ~Dev

Just did another test, going from Manhattan to West Point. Default (2500) takes about 28 seconds; using lane_speed = 3500 took about 20 seconds. That’s in SP, though, s’pose I better test MP… Yep, same.

It wasn’t in the freelancer.ini. I narrowed the source of the problem down to the script.xml. I’ve looked in the script, and it looks OK (and the mod works fine, and the only scripted option works perfectly), so I think FLE’s just getting confused.

I’ve got the team’s coder going over it with a fine-toothed comb, but I suspect I’m a victim of FLE’s buggy nature rather than a mistake in the script.

There is, however, a penalty in activation speed when using FLMM’s built-in generation, since the DLLs must be recreated every time, as well as a penalty for building the mod itself (needing to activate/deactivate each time DLLs change).

Traditionally, one makes a new DLL by copying an existing DLL and emptying it. There have been downloads of such DLLs, but apparently they are not here anymore, so I went ahead and attached the one I had from Giskard in this post. Just copy it, rename it, add it to your DLLs list and you should be set. It has a few “dummy” entries, but FLDev can quickly remove them.

Yep, that was the problem. I did the MAT manually in UTF editor 2.1, thinking that was the most recent. 3.0’s much better.

Thanks, glad you like them. I will post more pictures as I finish things. I will probably start a different thread for it though.

Glad it worked out for you guys. It was a team effort finding it 🙂

Well, I tried adding the space_farclip option and I notice something odd. If I look at the star from a distance obliquely (in turret view with ship neither pointed directly away or towards the star) I can see the effect at 26k away. But, if I’m in cockpit view looking directly at the star from that same point, it doesn’t show unless I turn the ship away.

This is my entry:
[SystemInfo]
space_color = 0, 0, 0
local_faction = li_p_grp
space_farclip = 100000

Yeah, yeah… I know. li_p_grp???!
I’ll get rid of that in the next iteration…

spin rate of 0.05 works great btw.

Edit:
After further playing with it I notice that if the solar is in the very corner of my screen in such a manner that I can not actually see the star, but rather just the edge of the rings I can see the effect at around 33k, but not further away. The moment I turn my view so that the solar is visible, the effect disappears until I’m at around 25k away. At that point the solar will remain visible regardless of view angle.

So, 0-25k effect is visible regardless of view angle
25k-33k, effect is visible only from an angle and the solar is off to the side of the view screen.

33k effect is not visible at all.

Figured it out:
Somehow I had two entries for the effect in effect_types.ini.
Getting rid of the incorrect entry fixed it. Working perfectly now.

Well, that fixed it. Thank you very much for the heads up on that, I was getting very frustrated by this point.

Now I can move on to breaking something else (and learning useful stuff in the process).