kenkasce.blogg.se - Basilisk emulator pre

#Basilisk emulator pre full#
#Basilisk emulator pre code#
#Basilisk emulator pre plus#
#Basilisk emulator pre mac#

If over time JTL comes out against the pre-CU milestone (SWGEmu 1.0) then that might become part of future server(s) as an expansion release.

#Basilisk emulator pre code#

We won't block others from running from the pre-CU code base, but we also don't want to be constrained by the pre-CU goal going forward. Mainly we want to get to a point where vanilla pre-CU experience is available (short of JTL) and then open up to new ideas for future SWGEmu official server(s). We see SWGEmu 1.0 (pre-CU) as a milestone in the code base, where it makes sense we will back-port changes to pre-CU (bug fixes, stability, JTL etc.).

#Basilisk emulator pre plus#

But this opens up another dialog about "not a pre-CU" experience, plus dealing with 100's of bug reports "Hey my ship doesn't move" will become a big distraction for the team. To be clear, we are not certain what if anything from JTL will be included in 1.0, we have debated some features being included (travel, space crafting). We have numerous ideas in this direction, and for me personally this is more interesting than waiting 5 more years while we try to reverse engineer more of JTL. We will hit the 1.0 milestone (no dates yet) and then launch a new server that will include on-going content expansion and other things the "new" server community will be passionate about.

#Basilisk emulator pre full#

No matter what happens we are progressing towards 1.0, just at this point we do not see a path that includes full JTL emulation for it. I would be happy to see a new "SIG" (Special Interest Group) form around JTL in the swgemu community, if we can find a couple talented and passionate devs who would like to leverage our CI/CD pipelines, test hosting etc then I'd be more than happy help and support. It was "ok" to me but never inspired me, I'm a MMO guy not a FPS'er or 3d Space kind of player. I personally lack the drive/interest/passion to make the space game work. Now all this said, it CAN be done, its a lot more work than any of the current devs can afford to dedicate.

In space nobody can hear you scream!!!!.

core3 was not designed for "ticks", we might be able to hack it in but it would be a nightmare.

Since the game was written by different devs, some subtle things are different like the coordinate system is not the same as the ground game (i.e.

In space, projectiles "tick" (they move in a direction with a velocity) and they collide with another object, on the ground you can't dodge a rifle shot, in space you can dodge a missile.

JTL is a space game, the ground game is not really 3d, so we need different spatial indexing tech.

But as we started to dig in deeper some of these things really smashed our hopes and dreams: Either drag or add to the list of hard drives and see if it mounts OK.We did a lot of investigation, I don't want people think we just threw our hands up, a couple devs (I won't name names) beat their brains out on it for months and made some progress here and there. In order for image files to mount, they need to be in a suitable format, i.e. If your B-II session is windowed and not full-screen you can also drag an image file from your host computer into the B-II window and it will mount as a disk drive this way, too. This way large image files will mount on the emulated desktop as a hard drive disk and you can access the contents that way, negating the need to create a drive for it. You can also, mount large image files in the emulator by adding them to the list of drives before starting an emulated session.

#Basilisk emulator pre mac#

You can easily create further classic Mac "hard disk" image files much larger than 500 MB and mount them in the same emulated session. It is very dangerous to work with files in the "unix" drive other than as a "go-between" as classic Mac files can be made unusable if run from within this drive. The "unix" drive should only be used to transfer files between the emulated hard drive and the host computer. "cannot be mounted from the disk it is currently on"