Thanks!!!

Thanks a lot, will do as you say.

Thanks a alot. I thougt it was much easier though, simply couple of .ini edits…

Ofcourse I thought about it, but this way it won’t “track” targets(target cross is in the same place while the target moves, not ahead of it like with guns), and it won’t be able to fire fast withot lag(some ammo is left near you and doesn’t fly away).

[dump_cargo]
at_t = 0.0000
orig_hardpoint = hpMount

File: fx/fuse.ini
Need to create new fuse and add it to the ship.

It helped me

Sorry my bad English

Example in fx/fuse.ini death_comm

Timmy51m wrote:
Weapons and such have explosion resistance entries in weap_equip don’t they? Perhaps that’s why they don’t go boom from normal explosions.

That’s not the case, it seems like fuse damage does not percepted by the hull as other types of damage(explosion and hits). didn’t try collision.

Found finally.

Kuze

Thanks.

One my computer with Windows 7 and bad videodriver, has casual crashes at launch from Monkey planet, with and without FlHook, binary patches and addition mod DLL.
On another computer with Windows XP and Windows 7, no crashes any time.
Some players has same crashes occured, other players no crashes any time.
I have found out that the pointer dword_674AA0 is equal to NULL in crash time, I do not know why so occurs, there Adoxa can be help…

Thanks anyway. Then the workaround is just to set NPCs not to loot nanobots/batteries at all.

OMG, it WORKS!!! it works!!!

I don’t no how you did it, but it works.

Really thanks!

HeIIoween wrote:
Nooo, then will be topics like

“Programming request: blahblahblah to blahblahblaing - how?” x))

Nah, people will get too lazy, I think it’s going to be kinda this:
“Programming request: blahblahblah to blahblahblaing - make a plugin” or something like that.

Noticed that mission weapon platform shoots non-mission weapon platform (!)

Problem activating deaths of nearby Solars that are destruct-able by their fuse from triggering generator_death_fuse on 1st Solar (it also vanishes after period of time).

[fuse] name = generator_death_fuse lifetime = 0.250000 death_fuse = true [impulse] at_t = 0.000000 damage = 1000000000 force = 1000000000 origin_hardpoint = HpFx13 pos_offset = 0, 300, 0 radius = 10000000

Me and objects survive while ignition object dies. What I do wrong?

Yeh I like his music but I’m not into raging poofters, especially ones who “marry” men, nor the bent society that lets them.

Bring on the 3rd Symphony! Or is it 4th? 5th? uh… whose, anyway? uh…

😄

OutCast wrote:
First, hitting FP9 domes, or anything attached with ‘parent’ to actual base won’t do any damage. I guess that’s your problem with Cardiff.

Yeah, I thought so, but it is not. I checked the part I launched missile at in hardcmp - it’s not a parent object.

Sure I will try testing without parent objects, but asteroid bases don’t have them - so I bet that the result will be the same as described above.

So I really wonder why cmp centre and slected base centre(the centre of the base when you select it in space) do not match.

OutCast wrote:
Second, when hitting asteroid-like base with missile/torp it won’t do damage unless it hits “metallic” part of it. Don’t know whether this is a material problem, or explosion ranges again.

By metallic you mean docking sphere?

some more questions:

1a).Why cmp centre and slected base centre(the centre of the base when you select it in space) do not match?
1b).How to make them match?

2.) Anything to do with asteroid-like bases?

Here’s a solution that effectively gives preference to space, rather than the HUD. You’ll lose the flashing icons and tooltips, but it’s the best I could come up with.

filler->0x6A01FF1580725C00E9C5000000 in freelancer.exe, 0x19DD72 = shoot through HUD PART 1 filler->0x84E40F8834FFFFFF31C0C3 in freelancer.exe, 0x19DE44 = shoot through HUD PART 2 0x75->0x67 in freelancer.exe, 0x19D207 = shoot through HUD PART 3 0x79->0x6B in freelancer.exe, 0x19E103 = shoot through HUD PART 4 ```For the curious: Parts 1 & 2 test if the left button is down (GetKeyState( VK_LBUTTON )); if not the HUD is ignored. Of course, I would rather ignore the HUD if the right button is down, but that was only partially successful, and I couldn't track down why. Parts 3 & 4 simply point to the new code.

There is an internal weighted vector which is used to determine how many ships should occur. This only goes up to 8, so adding more entries to NpcRank won’t do you much good. The weighting is at 11CC58 in content.dll (SP first, then MP; 0 & 1 are both 0):

Ships SP MP 2 3 2 3 9 3 4 6 9 5 2 6 6 1 4 7 1 2 8 1 1 ```This weighting ends up determining which rank will be selected for the job. Here's a patch to allow for 31 ships:

content.dll 0F8A4B 58CCFB->00CBFC = use 30-float array at 12CB08 (created manually!) for SP ship weighting vector ~adoxa
content.dll 0F8A54 7CCCFB->80CBFC = use 30-float array at 12CB88 (created manually!) for MP ship weighting vector ~adoxa

300f in content.dll, 0x116608, 0x117608 = multiplier for zone distance - increase to allow randommissions further from base ~adoxa

Increasing this constant too much may produce unwanted results:

If a vignette exclusion zone falls into this radius from a base, than vignette_exclusion zone is also accepted as a vignette zone(missions start spawn there, too). So 2 different players can get 2 different missions at the same place - looks weird.

So check vignette_exclusion zones positions after increasing above constant.

As was pointed out in another thread, the size of the zone does influence the distance that the center of the zone can be from a base and still give a mission. For a zone size of 10000, the center of the vignette must be within 34000 m (34km) from a base to give a mission; any further, and it won’t even be considered (unless a tradelane is involved…). Doubling the size to 20000 makes the limit 44000m (the formula is simply (vignette zone size + 24000)). adoxa found an offset that can change the 24000, too, which I’ve done. So it does affect something.

MK