Posts by dharthoorn

    After seeing some bright overexposure on some npc faces in ports with the CF ENB enabled I did a reinstall without the ENB plug. It did solve the issue but also now I have to miss the fancy lighting effects elsewhere...


    Then I tried my "standard" AA tool which I use for loads of games instead of the inbuilt AA (if any) because it achieves excellent results with minimal (if any) frame loss.


    Link;
    FXAA Tool


    Installation couldn't be easier;
    - Do backup the exe directory of freelancer because some files will be overwritten
    - Just drop the entire tool in the same folder as where the game .exe is located and you're good to go,


    Recommended FXAA settings;
    Settings


    Maybe I am not saying anything new to anyone but just saying there's an alternative... Really, it's worth a try!

    Thanks for all the comments and insights ;)


    I did a completely new install (even deleted doc folder & saves) and now homing seems to work again. I can also clearly see CM being dropped by NPC which didnt see before either. I guess one or more .fl files were corrupt...


    So clearly this was a user error of some sort and I'm sorry for blaming CF.


    In any case....back to driving the starflier -sigh-

    Yes, I found that out very quickly ;)


    I have blocked the app from connecting to the internet so my modded files stay modded. Now it just give me a time-out error E12 so that's fine.


    But seriously, nobode else has this problem in SP mode or are all you here playing MP? Even if I undo all my mods still the same pb I just dont get it.

    Sorry, but it just doesn't work.


    I have disabled all "equip = ge_s_cm_01" and "equip = ge_s_cm_02" with semicolons in the loadouts.ini file and the Stalker family STILL flies like javelins. What is even more infuriating; THEIR missiles DO lock & home! Even when I upgraded the missiles to "seeker_range = 3000" and "seeker_fov_deg = 360" my firestalkers still fly a dumb, straight line....


    It IS broken, beyond a shadow of a doubt, at least on my install. AFAIK I have not done anything other than follow the install instructions to the letter; clean fl install, flmm1.31, crossfire 1.9.


    Can you (or anyone else) verify my findings in SP mode versus AI on your own install? This is really a gamebreaker bug.


    @Martind Forlon
    Hello :) I'm afraid I'm just a casual player and this game is more than challenging enough for me battling a dumb AI in SP. And now that the AI has access to weapons beyond my reach it's just too difficult for me. Really the only thing I can do is mod out missiles alltogether but thats just lame because they were fun.

    Ah, I see.
    That nerfs missiles to an unacceptable degree IMHO. Statistically, I could easily waste 10 missiles per enemy even if they use the cheapest CM. Actually, thats whats happening now.


    Anyway, so technically, if I modify their loadouts to exclude any form of countermeasures the homing should work?

    Hello all, I'm new to the mod, and old to the game.


    One of the first things I noticed while playing in SP is that the Stalker family missiles do NOT lock and home anymore. I even checked (and modified) the weapon_equip.ini and in there seeking seems to be enabled. However in-game it does NOT work. I have triple checked this, double checked my findings, and then triple checked again after double checking to be sure. It is most definitely broken in single player vs. AI. Question is, is this deliberate or just a bug?