Librelancer 2019.08

[Ichiru]

Project Website: https://librelancer.net
Current Version: 2022.02. Download - https://librelancer.net/downloads.html

---

Flight Demo: January 2017

The Gameplay Demo option allows you to fly around a dodgy Defender!
Known issues in this demo:

• Sometimes crashes on startup with Intro Movies enabled. Make sure 'Skip Intro Movies' is checked.
  
• Asteroids don't collide.
  
• The physics in general is way off
  
• Some systems that worked before now crash: This is due to the particle engine failing to initialise (it's unfinished).
  

Download:

• Windows 7+
  
• macOS 10.10+
  

---

Sneak peak of the next upcoming feature...


(Click for full size)

DEMO UPDATED JULY 2016
Download:

• Windows 7+
  
• macOS 10.10+
  

---

Change for this version:

• Mac bundle!
  
• Suns
  
• Nebulae
  
• Improved planet rendering
  
• Intro movies
  
• Improved performance in general
  

If it doesn't work:
Post a screenshot of your error along with your GPU model and OS. (A really good way to catch errors is to run Librelancer under the command prompt so they don't go away once the program closes).

Demo Instructions:

1. Make sure you have the .NET Framework version 4.5.1 installed
   
2. Download the file
   
3. Install everything in the "INSTALL FIRST" folder
   
4. Start Launcher.exe in the Librelancer folder
   
5. Point the Launcher to your VANILLA freelancer folder, and have fun
   

---

So right here is a little project of mine I've been working on.
It's still in the early stages so there's not much implemented but...

It is a re-creation of the Freelancer engine, but cross-platform and all those nice things.
So far I have Newark Station rendering very nicely.


(Click here for full size)


(Click here for full size)
Right now it's pretty buggy, for example Planet New Tokyo looks like someone threw up all over it. (now fixed, but planets are still weird). It is progress, though. Contributions are always welcome. If you're a graphics programmer or just happen to know a lot about the Freelancer engine, skype me (or if you're brave enough submit a pull request to the project).

Demo will be coming soon™ (turns out there's a lot to do)

---

Acolyte of NoMe

[TheJarl]

Moved to 'Freelancer Forum'

Oh and of course, I like what you're doing even though I understand little of it. You already knew that though.

---

[The Savage]

I'm quite confused what OP is trying to do.

Okay, got it right now. An engine recreation... good thing! You should band up with @Swallow, I say.

[Swallow]

I'll stick to an ugly FL engine for now. Why? Becuase it is one love and one hate... Mixed feelings are the best.

---

FL MOD(EL)MAKING: TOOLS, RESOURCES, TUTORIALS AND MY SHIPS (OLD)

I am on discord: Roal-Yr#5994, I don't log on forum more than a few times a year.

I am not making ships for FL anymore, I am making my own space game instead:
https://github.com/roalyr/GDTLancer
https://roal-yr.itch.io/gdtlancer
https://youtube.com/playlist?list=PL5HQB...cdH45LZgjj

[Stuffz]

So I was looking through your code a bit and have a comment about that planet shader.

You write this:

Code:

out_texcoord = vertex_position;

and don't use your incoming

Code:

in vec2 vertex_texture1;

A texcoord can never be a vertex_position (uvs only go from 0 to 1 whereas local vertex positions go from -1 to 1)
And of course uvs are only vec2s instead of vec3 like you have in your

Code:

out vec3 out_texcoord;

This might fix your bug with the textures on planets not being right.

EDIT:

Also why the hell still use openGL version 1.4?

[Ichiru]

So I was looking through your code a bit and have a comment about that planet shader.

You write this:

Code:

out_texcoord = vertex_position;

and don't use your incoming

Code:

in vec2 vertex_texture1;

A texcoord can never be a vertex_position (uvs only go from 0 to 1 whereas local vertex positions go from -1 to 1)
And of course uvs are only vec2s instead of vec3 like you have in your

Code:

out vec3 out_texcoord;

This might fix your bug with the textures on planets not being right.

EDIT:

Also why the hell still use openGL version 1.4?

GLSL Version 140 isn't OpenGL 1.4.
GLSL Version 140 is OpenGL 3.1 lol

Also the New Tokyo bug was an issue with Bgra5551 textures not being loaded correctly which is now fixed. I am, however, going to replace the planet rendering code entirely since I need to use quad spheres instead of iso spheres.

---

Acolyte of NoMe

[Stuffz]

It still is an outdated version though and I doubt you really have a GPU that old.

[Laz]

I have no idea what the instructions mean. Anyway how is it built? How is it used?

---

[Laz]

No....?

---

[thisDerius]

Try not to make it too good. Not every PC can run the game that well. Especially Disco.

---