What I meant by limitation is that you are limited by what the engine allows you to do. In Freelancer, that’s really not much.

We’ve gone really far (and probably still can) with FLHook plugins, passionate starport devs tearing the game apart, various hacks and so on, but down the road we are always constrained by the engine in one way or another.

As a member of the SvenCoop team for several years now, I can assure you getting engine access changed our lives. This is what I want for Discovery. I want to be able to say something else than “No we can’t do that” whenever a community member asks about a feature that should be simple to implement, and instead be able to say “It’s possible but we’ll have to consider if it’s worth it”.

It will take a while to get somewhere, but we will.

Also, bear in mind we are working on it as a game of its own. We are not creating this as a modding platform. While mods may be possible, this is not a priority in our roadmap and it might never be if it ends up being a huge undertaking. There would be a higher chance of seeing the framework (without assets) opensourced.

Bolte wrote:
I keep coming back to this game, if I’m honest I made a lot of friends there that I wish I had kept in touch with. But started to get burned out of playing, and burned out on modding.

To me the community is what keeps the game going, but I feel that if only more people could access a version of FL where they don’t have to tinker and apply patches to get started, that we’d actually have some player growth.

Golden years over? Pah. We are in charge of that I think…

FL modding is very limited and very annoying to do.

That’s why the Discovery mod is in the process of being ported to Unreal Engine 4 by a secondary development team made of a few current developers in order not to affect the ongoing FL mod development cycle.

Same base game and behavior (as closely as possible), improved models and visuals while still compatible (hopefully) with toasters and later on new features once all the existing stuff is ported over.

We are very quiet about this project in general though, so don’t expect to hear much about it until we feel confident we have a playable beta.

Amazing work mate.

Besides the achievement this is going to be extremely useful for the freelancer community as compatibility issues keep arising with newer GPUs (like white textures/low LOD syndrome on AMD).

https://github.com/zibbizor/FLHook/releases/tag/v1.0

Use this package for starters, both conf and binaries.
All you need to run a server is ahookext, cloak and dsacesrv.

You will need the current discovery dsace.dll but also remember to have the directplay8.dll fix dll in the folder and registered in dacom.

You do NOT need dsace.dll referenced in dacomsrv…

This is a source code project. You will need Visual Studio to open a C# project to build/modify it.

This is excellent news, I’m working on a personal project these days and was in need of good dev assets.

You did a great job on these models. Thanks a lot for sharing!

Hey there,

Recently I’ve merged your ammolimit code into disco’s client hook with the intention of allowing variable ammo limits depending on launcher count.

I’ve actually worked on the server aspect of it first and it’s working as expected. Serverside I can use HkEnumCargo to get a list of the player’s equipment at any time but as expected that feature does not exist clientside.

While clientside there is CShip* cship = GetCShip(); and then I can traverse the equip manager… well that only works if the player is in space.

I’m looking for a way to access the player’s equipment/cargo while docked, any idea?

Thanks!

Well you will need a web server of some sorts, be it apache or nginx.

I’m looking at the code and I see some incomplete parts here and there so don’t be surprised if some stuff doesn’t work.

We’re going to need some specifics on what you want to do.

yeah the actual name is healing.dll

Why not just use adoxa’s repair dll? I’m using it for discovery and it works just fine, just need some flhooking done for scaling.

Huor wrote:
You dont really need milkshape at all. An image editing tool to create your icon. When saved as DDS you need to flip the image, saved as TGA can remain normal order.
You can use the model cloner tool to create a clone of an existing commodity icon, give it a unique new name, open up in UtfEditor, import the new icon and make sure the name and the node name match.

I tried the model cloner tool as well, under w10 I kept having weirdo issues which prompted me to go back to milkshape.

Though frankly with the template file it’s literally a 60 seconds job when you know where to click so I’m not too bothered about it anyway.

I was in need of an icon and tried to give a shot at Kazinsal’s FLIcon tool but it wasn’t producing any working icons for me, so I decided to wrap up a tutorial on the old fashioned way with milkshape as it was requested by the disco community.

You can find it here: http://discoverygc.com/forums/showthread.php?tid=132933

On which server did you see this?

Remember port forwarding isn’t all you need. If you use windows firewall you need to add an exception for your port otherwise it won’t show up.

You need to post here if you want your server to be listed. Discovery moved off from the global server list.

http://discoverygc.com/forums/showthread.php?tid=124653

Mystery solved completely randomly, turns out Tractor Beams and Armors will trigger it so it looks like this function is for internal equipment.

Has anyone ever found out in which situation ReqModifyItem is called?

I’ve been sorting out ReqRemoveItem, ReqEquipment and ReqAddItem, but in no situation I’ve ever been able to reach ReqModifyItem.

I’m not sure where the source for this is, but if you plan to bundle this in a mod and want a really simple solution, DSUpdate is probably what you should look into.

http://forge.the-starport.net/projects/dsupdate/files

Discovery used to use this for several years, but it was quite annoying to make incremental patches with it, so we moved to a launcher of our own not too long ago.

From the moment you make servers invisible if you don’t start the game through the launcher, people use it.

Hello,

I am aware of this limit and this is what surprises me. As you can see in the steps, adding more items do not cause the problem to happen, but one very specific amount will.

The exception thrown when this very specific amount of items is reached is the following: 0xC0000005: Access violation writing location 0x00000000.

Once I create the new vessel, the total count of items combined across all charfiles is:

177 cargo items
194 equipment items
which is a total of 371 items.

370 will work, 372+ will work. exactly 371 items will cause the account to be unloggable until someone removes one item.

I have attempted this on another account and you can hold 371 items, but with yoda’s account files, it won’t work.