Any work in SVN yet for moving towards new engine

[Rocfeather]

Has there been any work yet committed to SVN yet for the transition?  Or how do you imagine that work going?  Going to try to encapsulate/isolate the Crystal Space stuff?  Or will it be more of a ground up approach since I'd imagine the two engines would be fairly different in nature and not just something you can drop in and replace? 

[Venalan]

We have a separate (currently non-public) SVN with all the work which has been done on editing PS code to work with UE4. Talad is working on producing all the base functionalities necessary for PS to work, with help from a few people who are interested in helping getting the code ported to UE4. Last I heard he was working towards setting up stable client<->server communication which is a basic block of PS.

[Rocfeather]

Ah ok.  There is a fair bit of Crystal Space stuff that is not necessarily engine related as well.  Stuff like the smart pointers and some of the collections stuff would have to be cleaned up as well. 

[Eonwind]

People interested in contributing to port PS over UE con join #planeshift-prospects where you can join the effort and eventually get access to the not-yet-public SVN.

[CheatCat]

I think the Unreal Engine 4 port should be on a public SVN. Why? Because then everyone who wish to contribute to the UE4 port can do that, and everyone who want to play around with it can do that too in order to get interested. There could be some issues with this like things does not work and the project feels "broken" in general. I however would like something to work on and test without having to reinvent the wheel again.

[redhound]

I think the Unreal Engine 4 port should be on a public SVN. Why? Because then everyone who wish to contribute to the UE4 port can do that, and everyone who want to play around with it can do that too in order to get interested. There could be some issues with this like things does not work and the project feels "broken" in general. I however would like something to work on and test without having to reinvent the wheel again.

Vote for it - be more open, PS!

[Jilerel]

I think the Unreal Engine 4 port should be on a public SVN. Why? Because then everyone who wish to contribute to the UE4 port can do that, and everyone who want to play around with it can do that too in order to get interested. There could be some issues with this like things does not work and the project feels "broken" in general. I however would like something to work on and test without having to reinvent the wheel again.

Vote for it - be more open, PS!

^^^^^
This

[qwertymc2]

A private branch?  Are you kidding?

[Ravna]

Yes, a private branch, very observant.

As for the why, simple, it doesn't work, you can't use it to connect to the Laanx server, and most likely, you won't even be able to compile it. Now no matter how many times you write that in big letters next to the link to a public repository, people are still going to go there and try to compile it, and then come back disappointed or asking half a dozen questions that have no answers yet.  So the choice was made to make it a private repository until it at least is a decent working demo.

Also notice however, that private does not mean you cannot get access to it. It is not public, but if you want to work on the code, you can contact Talad, and he can give you access to it.

[qwertymc2]

Also notice however, that private does not mean you cannot get access to it. It is not public, but if you want to work on the code, you can contact Talad, and he can give you access to it.

And what if I simply want to read the git history and check by myself how the porting is going instead of wasting developers's time in the forums?

[Ravna]

That is unfortunately not possible, one of the downsides of the chosen solution I suppose. Though in all honesty, I don't believe much could be learned from those logs without also knowing the roadmaps/etc. But either way, unfortunately, no.

[qwertymc2]

Though in all honesty, I don't believe much could be learned from those logs without also knowing the roadmaps/etc.

In fact roadmaps/etc should be public too.

[MerxRort]

Does anyone now how to make a box blocking property and make it form onto the static mesh, like the SPHAT on DM anchorhead?

[MishkaL1138]

http://forums.sandcrawler.net/index.php?PHPSESSID=h5bimqctlrev010mm9dp89mff5&topic=1239.msg6242#msg6242

Now, if you will, please stick to the topic on hand 

[derula]

Year 17.
People still believe that PlaneShift is open source.

There is a difference between publishing your source code and making a stand for FOSS software. PlaneShift is, and always has been, proprietary. Access to the source code is only granted for the sole purpose of tricking developers into working for the project for free. Stop expecting this project to have an open source vibe to it. I know that they're saying it's open source, and pretend like this entails all the things you would expect from an open source project. And I don't even want to say they're consciously lying. Maybe they truly believe that. But if they do, they have no idea what FOSS software is all about. They don't fully understand the difference between "free as in beer" and "free as in freedom," and they never will. So stop expecting them to act like PlaneShift was Free (as in freedom) and Open Source, because it's not. It's a proprietary, freeware game, that allows access to its source code. No more, no less.


Edit: Yes, I realize I suffer the RAS syndrome. Sue me.