Nightdive says Dark Forces has been ‘difficult to change’ because LucasArts created its own version of multi-threading years before it became popular

@[email protected]

Is it the only Build engine game that did this? I don’t remember seeing any significant performance/grapical differences back when they were new.

@[email protected]

Is it the only Build engine game that did this?

It’s not a Build engine game: https://en.wikipedia.org/wiki/Jedi_(game_engine)

@[email protected]

Oh, cool!

It always felt like one, or at least I remember it that way.

Outlaws was the better game, IMO.

@[email protected]

I don’t remember seeing any significant performance/grapical differences

CPUs weren’t multicore back then, this wouldn’t have been to improve performance really, they’d use “green threads” to conveniently run code with waits in it, and it sounds like they had a task queue of green threads

Nightdive says Dark Forces has been ‘difficult to change’ because LucasArts created its own version of multi-threading years before it became popularplus-square

Nightdive says Dark Forces has been ‘difficult to change’ because LucasArts created its own version of multi-threading years before it became popularplus-square

Games

Nightdive says Dark Forces has been ‘difficult to change’ because LucasArts created its own version of multi-threading years before it became popular

Nightdive says Dark Forces has been ‘difficult to change’ because LucasArts created its own version of multi-threading years before it became popular