Oh my God!!! That ginger girl is the absolute doppleganger of my lady!! How come you know her ????? Gorgeous and sweet, hope your ginger is the same ; ) Thx for the game, i'll give it a try.
Rylee is a top tier LI for sure, so treat her wellOh my God!!! That ginger girl is the absolute doppleganger of my lady!! How come you know her ????? Gorgeous and sweet, hope your ginger is the same ; ) Thx for the game, i'll give it a try.
-----------------------------------------------------------------------------------------------------------------------------------Happy New Year from the Otter Team!
View attachment 1574684
Chapter 2 is coming this week. We can't wait for you all to play!
Posted June 12th and well...View attachment 1867012
Happy Otter-versary!
Matrix Hearts is officially a year old!
We have come a long way and have much, much further to swim yet. It's incredible that its already been a year, and although we wanted to have at least released 3 chapters already, we have made incredible progress regardless of setbacks, and we are now looking otterly better than before!
Even though we are only a year(ish) into development, we have gained incredible support from you, our fans and Patrons, and it is with that continued trust that we can accomplish more! And yes, more butts and boobs included.
Here is a special render from us celebrating our Otter-versary. Also, early access for v.0.2.2 is officially coming this week, with development in the renders for Chapter 3 now in full production.
Thank you, Otters, and keep those whiskers playing!
-The Otter Team
the thing i dont agree here would be "hype" thing - not sure "hype" would be a proper term for no an actual update yet a kinda patch for the previous one-----------------------------------------------------------------------------------------------------------------------------------
Posted January 1st and then it took a month for it to get released
-----------------------------------------------------------------------------------------------------------------------------------
Posted June 12th and well...
There appears to be a communication error between those doing the work and whomever handles posts. False and misleading hype is becoming a pattern.
Thanks, Abhai!the thing i dont agree here would be "hype" thing - not sure "hype" would be a proper term for no an actual update yet a kinda patch for the previous one
we are still far away from the proper 0.3 update (end of the year, id say - perhaps some haloween mini "special" or so)
the game is very good, yet 8-12 months updates schedule is a bit less "good".
at the end, it is irrelevant - as long as patrons are happy/hooked, nothing else matters much, particularly "complains" of filthy pirates
It's a marketing strategy. Most devs experience an increase with a release. Announce a release is imminent at the beginning of the month causing subs to go up. Wait a week or two and announce small insignificant delay. Wait until the next month to release. Now those who only sub for a single month when releases drop just stuck around for two. Hence the early and seemingly false hype. Not a smart long term strategy for a fairly new dev team unless they don't intend to see this project to completion and change to a different name after the pattern is more widely recognized and subs start dropping.the thing i dont agree here would be "hype" thing - not sure "hype" would be a proper term for no an actual update yet a kinda patch for the previous one
we are still far away from the proper 0.3 update (end of the year, id say - perhaps some haloween mini "special" or so)
the game is very good, yet 8-12 months updates schedule is a bit less "good".
at the end, it is irrelevant - as long as patrons are happy/hooked, nothing else matters much, particularly "complains" of filthy pirates
Thanks, Abhai!
Interesting that this is what he put his time into, but we understand. Perhaps if people are so interested, they should instead look at our other posts on Patreon to see why these games were delayed unexpectedly.
Chapter 2 was delayed because our artist had real life obligations that kept putting us behind when we thought things were on track.
Chapter 2 v0.2.2 was delayed because that same artist couldn't work on the game anymore and our Main Otter had to learn Daz and Animations from scratch with help from other people. You can ask any of our playtesters that have been playing versions of this that it has been a steep learning curve.
Even when things do get delayed, we are very transparent as to exactly why, and usually it's been because of a newbie error on rendering or animations which have now been fixed and learned from.
Developing a visual novel is not an exact science, and it's even more so when one Otter goes from writing and programming... to literally doing everything.
These little hitches are a huge boost in production later on though, as we have learned and now won't make those mistakes again, meaning we get into smoother production.
As for Chapter 3, you are right on the money, it's probably going to come out between Halloween and Thanksgiving.
Oh, and the new 0.2.2 update is already in early access, so we are releasing that on the 28th! Thanks to our players and Patrons who have understood and stuck by us! The game is going to play, sound, and feel the same because of the hard work from the Otters, only with slightly upgraded graphics!
It's that game production life!
This is your post saying chapter two was delayed because 200 renders were bad and nobody noticed it until the last moment not because someone had IRL p problems.View attachment 1587248
Being an Otter means learning as you go, and now we've learned quite a bit!
We were supposed to get Chapter 2 out weeks ago, and then it was early this week.
Weeeeell, we had all the renders complete, and then as we were looking over the images, we noticed these weird blemishes on about 200 of the renders. We think it's because of the specific lighting we were using, and we managed to fix it after a few goes of it. The new renders are pumping now as our little paws type. We aren't going to give an exact date because every time we do, we run into a beaver dam. Those damn beavers.
Trust us, it won't be that much longer! We appreciate your patience as we continue to learn and grow as whisker developers. We have played through it ourselves though, and we don't mean to brag, but we were smiling! This is going to be awesome!
- The Otter Team
Read our posts from earlier. Not one post.This is your post saying chapter two was delayed because 200 renders were bad and nobody noticed it until the last moment not because someone had IRL health problems.
I have read all of your posts. That is why the pattern is so obvious. Either your people are putting you in a position to look disingenuous or it's an agreed upon situation by you as well. Do what you like. It's your reputation on the line.Read our posts from earlier. Not one post.
Reading this, please allow me to give my input from my experience working with Blue Otter Games. Although I was not there, assisting development in January when the post was made, both statements are true.I have read all of your posts. That is why the pattern is so obvious. Either your people are putting you in a position to look disingenuous or it's an agreed upon situation by you as well. Do what you like. It's your reputation on the line.
Then allow me to put this as simply as I can. Your reputation (what I know of it from reading many of the threads here) is virtually pristine. I don't think I have ever read a single thing that would suggest you are anything but helpful and professional. The team you are now working with has an issue. The mouthpiece speaking before he has all the info he needs or team members being dishonest with him about what is and isn't done. That isn't a non-issue when it's already becoming a pattern. Not if the brand means anything long term.Reading this, please allow me to give my input from my experience working with Blue Otter Games. Although I was not there, assisting development in January when the post was made, both statements are true.
Blue Otter Games and I started discussing my joining the team in late March. At that time, the previous artist otter had almost completely left the team and was already, at best, extremely difficult to get a hold of due to real life obligations. and even before then, their obligations were steadily increasing.
When you're under a significant amount of stress in your real life, compounded by a need for high render throughput, you will be forced to skimp on quality. There is a middle ground between how much of a delay is necessary and how much you skimp on quality, and the decision was made somewhere in the middle. You lose some quality in favor of a high number of renders. Unfortunately, this does result in some renders simply not coming out right.
Here is an example of one of the earliest renders I put out for CH2.2. (Please know that all renders from this scene were later replaced). Notice how the haircap is clipping through the skull and causing black lines. This is a very common issue with Daz, and one which is easy to fix in Daz, but very hard to notice before the final render. The only alternative to a rerender is Photoshop, which, depending on experience level, may not have any time savings compared to the insane load times of Daz.
View attachment 1893168
For Ch 2.2 to happen, a lot of people have had to step up. The writing Otter, who has previously never used Daz (or any 3D software whatsoever), has learned how to pose on it, I learned Daz's rendering system (I have never rendered in Daz and instead rendered with outside programs), and further outside help has been needed to fill in gaps in either of our knowledge. I am incredibly proud of what we have achieved, despite the delays, and the fact we have gotten this far with the incredible amount of shit that has gone wrong is amazing. (We've had everything from time crunch to hardware failures).
Chapter 3 will be a rough update to get out. The issues which have impacted CH 2.2 continue to exist and we have further issues which will cause us a great deal of trouble. We pledge to do everything in our power to get CH 3 as we can but it isn't going to be easy.
Out of this conversation, there is one point which I do agree with you on. Blue Otter Games is incredibly optimistic on deadlines. For this Chapter 2.2 update, some of it is my own fault, however. I believed I could achieve a rate of renders that I simply could not, and that reflected in the projected release dates. However, that is something that I will personally ensure does not happen again.Then allow me to put this as simply as I can. Your reputation (what I know of it from reading many of the threads here) is virtually pristine. I don't think I have ever read a single thing that would suggest you are anything but helpful and professional. The team you are now working with has an issue. The mouthpiece speaking before he has all the info he needs or team members being dishonest with him about what is and isn't done. That isn't a non-issue when it's already becoming a pattern. Not if the brand means anything long term.
And issues will always come and go. You're doing the best with what you have. Simply put, there really isn't a reason to beat a dead horse. It's now a subject for you and your team to discuss or not discuss.Out of this conversation, there is one point which I do agree with you on. Blue Otter Games is incredibly optimistic on deadlines. For this Chapter 2.2 update, some of it is my own fault, however. I believed I could achieve a rate of renders that I simply could not, and that reflected in the projected release dates. However, that is something that I will personally ensure does not happen again.
I have made posts (1, 2) describing why things are how they are, and I do not blame Blue Otter Games for not fully understanding the exact issues we face. Almost all the issues we face simply don't appear, or otherwise are almost impossible to notice, with the Texture Shaded or Smooth Shaded views of Daz, which is what they're restricted to (no nvidia gpu to render, and cpu rendering is one of Dante's circles of hell).
Take the hair clipping for example, that bug can almost invalidate an entire day of work since most of the time is not spent fixing up the scene to render, but instead just loading the scene in the first place. (Depending on the scene and number of characters, it can easily take >10 minutes each. Even rendering itself only takes 8 minutes after it loads.). Fixing the hair bug itself can take as little as a few seconds afterwards.
As I was working through those early renders, I first thought I was capable of a certain rate, but due to not only Daz making my life unnnecessarily difficult, but also real life, I found I was not able to maintain such speed, causing the update to be forced to delay as a result.
If you wish, you are welcome to contact me through any means appropriate regarding the game. I can not tell you anything I won't say publicly, but I can answer questions and take in criticisms.And issues will always come and go. You're doing the best with what you have. Simply put, there really isn't a reason to beat a dead horse. It's now a subject for you and your team to discuss or not discuss.
Honestly, I was pretty thrilled to see a Canadian based team pop up and with a fairly unique concept so far. If all of this ends up a distant memory, then that is good news for all involved. Not saying something wasn't going to help see that happen though. If I knew you were on team Otter, I probably would have shot you a PM yesterday instead of posting today because your reputation speaks for itself.
Thank you for the input!Out of this conversation, there is one point which I do agree with you on. Blue Otter Games is incredibly optimistic on deadlines. For this Chapter 2.2 update, some of it is my own fault, however. I believed I could achieve a rate of renders that I simply could not, and that reflected in the projected release dates. However, that is something that I will personally ensure does not happen again.
I have made posts (1, 2) describing why things are how they are, and I do not blame Blue Otter Games for not fully understanding the exact issues we face. Almost all the issues we face simply don't appear, or otherwise are almost impossible to notice, with the Texture Shaded or Smooth Shaded views of Daz, which is what they're restricted to (no nvidia gpu to render, and cpu rendering is one of Dante's circles of hell).
Take the hair clipping for example, that bug can almost invalidate an entire day of work since most of the time is not spent fixing up the scene to render, but instead just loading the scene in the first place. (Depending on the scene and number of characters, it can easily take >10 minutes each. Even rendering itself only takes 8 minutes after it loads.). Fixing the hair bug itself can take as little as a few seconds afterwards.
As I was working through those early renders, I first thought I was capable of a certain rate, but due to not only Daz making my life unnnecessarily difficult, but also real life, I found I was not able to maintain such speed, causing the update to be forced to delay as a result.