Thanks Will continue and currently working on the next features (this time the focus is helping modders).
Server Admins
Grants access to the Server Admins Anomaly category in the archive
Posts
-
-
Regarding the SVN problem: My suggestion is to start the SVN server, check each repo out with git SVN brigde (e.g. Tortoisegit has it integrated right into the clone dialog) and then upload it as a git repo. You can have the full history from SVN this way. You just need to do this correctly. I have some SVN repos checked out as git repo just before it got shut down this way. But not all of them.
-
I finished beta 2.1: Download beta 2.1
The focus was mainly rendering bugs / improvements.
Changes are:- Fixed rendering bugs with old lighting (affects also starspheres etc.)
- Made old lighting very similar to FL lighting (including cubemaps)
- Had a nice idea for nebula ambient lighting. It now is complete PBR lighting
- Added option to enable point lights for new lighting. Make sure to remove e.g fake planet reflection point lights from FL system inis before enabling it (will look weird, since planets are like suns then). To enable it, set EnablePointLights=1 in config.cfg.
-
Heya everyone. I was wondering if anyone knows what function within Freelancer.exe I can call to cause the the ship to flip between it’s various camera states. I am looking primaraily to convert between the normal view and cockpit view on demand, as well as preventing the user from manually switching back if possible, but I have a few different ways to achieve the latter.
Spent a while looking in IDA trying to follow what happens after the user presses the H key (for turret view) and the like, but can’t seem to find where the game changes the state.
Any help appreciated!
-
I updated the documentation thread with instructions how to fix problems with DPI scaling.
Also I forgot to mention which format the normal/rougness/metalness maps use. This is also in the documentation now. -
I had the explosion lights working before. The thing is FL likes to fake lighting stuff with vertex colors - so I do not want to answer that right now without further testing.
Edit: I tested it and explosion lights work again after enabling point lights. So I suggest you just test the next version I will release (should be in the next weeks).
-
To make this more clear I added it to the known issues list.
I disabled the point lights because vanilla FL uses them in many systems for fake planet ambient light reflections, which look weird without shadows. Also if those lights have shadows enabled they are too close to objects and the shadows break.I will add a developer menu soon where you will be able to enable them. But if you don’t change the system inis lighting will be weird then at those places.
I never tested spot lights, so I will have to enable them and see if it works. They will for now not have shadows, though. If they work I will enable them by default.
I will add some other useful stuff to this menu, like reloading all textures (only in FLARDATA\textures), reloading the materials.json, reloading shaders and I also think about adding adoxa’s hook for reloading the system in case it also reloads the models (not tested yet). This should really help for live testing stuff.
Also as I already wrote in discord chat to @HeIIoween, you should not reduce metalness too much if the material is metal. I just write it here again so that people do not get bad advice. You can see here, what happens if you do that (it behaves more like e.g. plastic or ceramic).
I also added some more PBR links to the documentation (more to come).
-
The default settings in materials.json are more a rough orientation. They are used in our mod, where I have proper roughness and normal maps.
Note that I released the beta also so that people can understand better how PBR works. You will have to adapt your mod if you want to use it.
Also what you disabled there is the tonemapping, which just caps the maximum light value to 1. It is not a fix.
There will be another factor you can change soon: It is the exposure value, which already is used and currently set to a fixed value. I did not add this on purpose yet, because I am afraid people will use it wrong.
The idea is that you can change it in the config, or that I allow a value to be set per system. I also will experiment with automatic exposure control later. -
For PBR rendering this also depends on your light source. With old lighting, the light intensity was in range from 0-1. With PBR you can have 0-infinite (or rather max float, due to hardware limitations). This is why I added tonemapping. It makes it look more like film (yes, analog film) would behave. I will try to explain this later in more detail in my documentation.
In short if you don’t want to have it so bright:
- Change roughness of material
- Reduce light color intensity of light source or reduce its range
Note that the viewing angle also plays a role.
-
Yes, if a constant value is not enough, then you need to craft special roughness/metalness maps. Otherwise just create a new entry in materials.json or use an existing one which is working for that.
Since a lot people asked about that (especially custom planet textures) I added some text about it to my release post.
@NeoTendar: Thanks! Yeah you can leave them empty if you do not need any text.
Release: Advanced Renderer public beta 2.1
TSP Community To-Do List
Release: Advanced Renderer public beta 2.1
[Hack Request] Changing camera mode programatically
Release: Advanced Renderer public beta 2.1
Release: Advanced Renderer public beta 2.1
Release: Advanced Renderer public beta 2.1
Release: Advanced Renderer public beta 2.1
Release: Advanced Renderer public beta 2.1
Release: Advanced Renderer public beta 2.1