0.44.0 isn't out yet, but since we make so much progress with 0.45.0 I'll start with this thread anyway.
We already have 32 closed issues, more than a third of the total issues for 0.44.0. A lot of these are more substantial changes with more potential for things to go wrong unexpectedly. We definitely will need a lot of testing on this one. But if everything works out we have another massive release on our hands.
I recently saw a life-sign from unelsson. He will not immediately continue with his work on the editor, but it looks like we can expect more from him in the not too far future. Still, we need more help on the editor, if we want to have OpenMW 1.0 and OpenMW-CS 1.0 ready at the same time.
OpenMW 0.45.0
Re: OpenMW 0.45.0
Hey,
I want to contribute to OpenCS but I am a 3D Artist. What can I do to help?
Happy to see that OpenMW and OpenCS is moving at such a fast rate. Looking forward to the 1.0 release.
I want to contribute to OpenCS but I am a 3D Artist. What can I do to help?
Happy to see that OpenMW and OpenCS is moving at such a fast rate. Looking forward to the 1.0 release.
Re: OpenMW 0.45.0
No work for a 3D artist on OpenMW-CS, I am afraid. The example suite project (viewforum.php?f=25) may have need for an 3D artist.
-
- Posts: 27
- Joined: 31 Jan 2015, 15:23
Re: OpenMW 0.45.0
I was honestly beginning to worry the project was going to fall apart from the buyout for a little while there. Glad to see work is still going
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: OpenMW 0.45.0
Although I think everyone could have done without the drama. If anything, it's kinda given everyone the motivation to prove all the Negative-Nancies wrong.
Re: OpenMW 0.45.0
We're an open source project and that comes with the territory. We should probably put out a call for more developers with the next news post. We don't need to mention why, exactly.
We should also write down somewhere what happened, as future project fans may want to read about it in the history of the project. It IS interesting that a largely publicized buyout caused as far reaching consequences for a major developer of ours.
We should also write down somewhere what happened, as future project fans may want to read about it in the history of the project. It IS interesting that a largely publicized buyout caused as far reaching consequences for a major developer of ours.
Re: OpenMW 0.45.0
Who isn't with us anymore? Are you talking about scrawl? I thought he was still going to be involved just more indirectly. Sorry, I stopped following the GitHub thread once it devolved into multiple pages of shouting.
This is great news! I know I haven't done jack to help anything for a long time, but I'm starting a new job in a few weeks and have some time off in between so I'll probably try and get some more work into the docs.Zini wrote: ↑13 Jun 2018, 17:38 We already have 32 closed issues, more than a third of the total issues for 0.44.0. A lot of these are more substantial changes with more potential for things to go wrong unexpectedly. We definitely will need a lot of testing on this one. But if everything works out we have another massive release on our hands.
- AnyOldName3
- Posts: 2685
- Joined: 26 Nov 2015, 03:25
Re: OpenMW 0.45.0
Scrawl had already stepped back to a barely involved at all level, and during The Great Kerfuffle declared that he wasn't going to be involved at all any more. I'm not sure if we think he might be willing to do a once-over on Zini's post-1.0 document, but everything else is most definitely off the table for the foreseeable future.
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: OpenMW 0.45.0
I think that if Blue delivers on his windows only fork that Scrawl will deliver on his linux only fork just out of spite.
- drummyfish
- Posts: 154
- Joined: 22 Oct 2017, 10:13
- Contact:
Re: OpenMW 0.45.0
Probably no way to help directly, but you can at least test the quality of the 3D view and manipulation and give feedback, since you have experience with that. Other than that I'd also like if you helped the example suite project, that's where you could shine