@Benjamin
Knock, knock.

(11-09-2018, 02:30 PM)Benjamin Wrote: UMOP2 links are up.

@Benjamin Hey buddy I downloaded v2 45mins before you posted the above.

Everything seems to check out with the MD5sum check thing too.

So was it up 45mins ago before you wrote the above?

(11-09-2018, 01:38 PM)DarthXedonias Wrote: @Shannon Hey, I just wanted to ask is the plan for 3.3 to still have it come out by November 20th even if you weren't able to add everything you wanted?

I'm planning to work on it until my gut tells me it's good to release. If that happens on or about the 20th, great. If not, I'll keep going.

Quote:Also, there were two other question I had. Were you able to fully update the Magnus engine?

I haven't had the chance to work on that yet.

Quote:I remember you kept saying that was going to be the most time consuming part. Also, on the reality bending side were you able to find any other ways to improve the reality bending? Or have you pushed it as far as you safely can?

Reality bending is at v5.1, and that's as far as I know how to push it right now without causing problems.

Can someone confirm that the break after E2 is only one week(and not 21+ days as the other 5.5G subs require)? @Shannon @Benjamin

(11-09-2018, 02:31 PM)AlphaRomeo Wrote: @Benjamin
Knock, knock.

Haha, whos there?

(11-09-2018, 02:33 PM)Jake2015 Wrote:

(11-09-2018, 02:30 PM)Benjamin Wrote: UMOP2 links are up.

@Benjamin Hey buddy I downloaded v2 45mins before you posted the above.

Everything seems to check out with the MD5sum check thing too.

So was it up 45mins ago before you wrote the above?

Yeah I had done it a bit before posting, I was doing other things then thought I better make a post. It says V2 in the filename.

(11-09-2018, 02:37 PM)ianmarconi Wrote: Can someone confirm that the break after E2 is only one week(and not 21+ days as the other 5.5G subs require)? @Shannon @Benjamin

Yes a week is fine for E2.

(11-09-2018, 02:37 PM)ianmarconi Wrote: Can someone confirm that the break after E2 is only one week(and not 21+ days as the other 5.5G subs require)? @Shannon @Benjamin

E2 does not have P5/P6. A good rule of thumb in that case is Generation + 1 day per month of use.

E2 is the first 5.5G sub, which rounds up to 6 days off. Then add one day rest for each month of use.

Most people just do a week.

(11-09-2018, 02:43 PM)Benjamin Wrote:

(11-09-2018, 02:31 PM)AlphaRomeo Wrote: @Benjamin
Knock, knock.

Haha, whos there?

"Reverse home delivery", I was about to say.
I was close, but you were faster. Check the timestamps of our earlier posts...you delivered and I didn´t even see, while being busy knocking the door lol.

(11-09-2018, 02:34 PM)Shannon Wrote:

(11-09-2018, 01:38 PM)DarthXedonias Wrote: @Shannon Hey, I just wanted to ask is the plan for 3.3 to still have it come out by November 20th even if you weren't able to add everything you wanted?

I'm planning to work on it until my gut tells me it's good to release. If that happens on or about the 20th, great. If not, I'll keep going.

Quote:Also, there were two other question I had. Were you able to fully update the Magnus engine?

I haven't had the chance to work on that yet.

Quote:I remember you kept saying that was going to be the most time consuming part. Also, on the reality bending side were you able to find any other ways to improve the reality bending? Or have you pushed it as far as you safely can?

Reality bending is at v5.1, and that's as far as I know how to push it right now without causing problems.

For DMSI 3.2, which version of reality bending was it at? Was it v2 or v3?

(11-09-2018, 01:38 PM)DarthXedonias Wrote: @Shannon Hey, I just wanted to ask is the plan for 3.3 to still have it come out by November 20th even if you weren't able to add everything you wanted?

(11-09-2018, 02:34 PM)Shannon Wrote: I'm planning to work on it until my gut tells me it's good to release. If that happens on or about the 20th, great. If not, I'll keep going.

Quote:Also, there were two other question I had. Were you able to fully update the Magnus engine?

I haven't had the chance to work on that yet.

Quote:I remember you kept saying that was going to be the most time consuming part. Also, on the reality bending side were you able to find any other ways to improve the reality bending? Or have you pushed it as far as you safely can?

Reality bending is at v5.1, and that's as far as I know how to push it right now without causing problems.

(11-09-2018, 03:45 PM)wolverine_i_am Wrote: For DMSI 3.2, which version of reality bending was it at? Was it v2 or v3?

http://www.subliminal-shop.com/product/d...y-3-2-a-b/
Product Description:
– DMSI 3.2 Change Log –
38. Upgraded Reality Bending to V5.0

@Shannon I don't know if I might be in the minority or not, but I'm cool with the possibility of DMSI 3.3 not being ready by November 20. WordPress 5.0 is slated for release Nov 16 or so and they still have hundreds of outstanding bugs they want to take care of before then, and that's a team of a few main devs and anywhere from a dozen to maybe a hundred decently skilled open-source contributors on top of that. You're one guy and I could understand if simply the amount of work alone, not to mention other possible real-world factors, might result in taking longer than the last week or two of this month.

(11-09-2018, 07:37 PM)apollolux Wrote: @Shannon I don't know if I might be in the minority or not, but I'm cool with the possibility of DMSI 3.3 not being ready by November 20. WordPress 5.0 is slated for release Nov 16 or so and they still have hundreds of outstanding bugs they want to take care of before then, and that's a team of a few main devs and anywhere from a dozen to maybe a hundred decently skilled open-source contributors on top of that. You're one guy and I could understand if simply the amount of work alone, not to mention other possible real-world factors, might result in taking longer than the last week or two of this month.

I appreciate that.

Things are not done here the way other subliminal producers do them. Gone are the days when I could just write a script and optimize it by hand and then build it. In those days, I could build a program relatively quickly. Now it can sometimes take me days to craft a single sentence correctly, looking through literally hundreds of possible variants to get the highest possible levels of optimization.

I don't go to quite that degree very often, because it is rarely necessary, but it can easily take me 6 to 12 hours just to get one statement fully developed.

And a module may contain between 1 and more than 24 statements.

On top of that, consider that there are multiple sections of script (Pre-Script, Key Script, Core Script, Skeleton Script Body at the least) and that each one contains multiple modules, sometimes numbering more than a hundred.

Then consider that upgrading DMSI means I have to adjust, change, optimize, add to and/or replace some or all of each of those sections, with multiple modules each, usually having multiple statements each, without breaking inter-operability and inter-dependencies.

Finally, in DMSI, each statement can be pages of text long. So it's not exactly easy to work with them and maintain grammatic correctness. Even after all these years of doing this, I have to work on each statement in staggered sections that overlap to make sure the grammar is perfect.

And then you have the fact that I have a life, just like anyone else, and shit likes to happen to me.

So I had to build USLM3 and UMOP2 before working on DMSI 3.3 again, and that is done, and I spent the rest of today resting. I almost burned myself out trying to get all that done so fast.

Now I will resume working on DMSI 3.3, but I don't want to release it without having made enough improvements to it to be worth my time and yours. There is a lot left to do, so I'll be working hard, but setting deadlines when it's not absolutely necessary tends to result in dissapointment.

Of course I know there are some of you who think I'm silly for not using deadlines more often, but I know two things are true when it comes to deadlines.

First, they almost always result in less good quality than just working steadily until the job is done.

Second, I personally don't do well with deadlines.

So since you guys are waiting for something good, we might as well work on it right and do what it takes to get the best results we can get.

That said, I don't know when it will be finished; it might be on or about the 20th, still. Or it may be later. But for those of you who have a problem with it taking so long, I can only say that in my shoes you would be in the same position.

Doing it right is better than doing it fast. Complaints on this can be filed in the circular file. Working at my own pace, and in my own way, is how I achieve programs worth paying what we charge for them.

You guys are going to see what DMSI Final is like soon enough. It's not too terribly far off at this point. Especially with this cycle ending at the end of December. Maybe then, we can return to building it every couple of months.

I am definitely ready to be done with DMSI AND developing 6G!

(11-09-2018, 08:03 PM)Shannon Wrote:

(11-09-2018, 07:37 PM)apollolux Wrote: @Shannon I don't know if I might be in the minority or not, but I'm cool with the possibility of DMSI 3.3 not being ready by November 20. WordPress 5.0 is slated for release Nov 16 or so and they still have hundreds of outstanding bugs they want to take care of before then, and that's a team of a few main devs and anywhere from a dozen to maybe a hundred decently skilled open-source contributors on top of that. You're one guy and I could understand if simply the amount of work alone, not to mention other possible real-world factors, might result in taking longer than the last week or two of this month.

I appreciate that.

Things are not done here the way other subliminal producers do them. Gone are the days when I could just write a script and optimize it by hand and then build it. In those days, I could build a program relatively quickly. Now it can sometimes take me days to craft a single sentence correctly, looking through literally hundreds of possible variants to get the highest possible levels of optimization.

I don't go to quite that degree very often, because it is rarely necessary, but it can easily take me 6 to 12 hours just to get one statement fully developed.

And a module may contain between 1 and more than 24 statements.

On top of that, consider that there are multiple sections of script (Pre-Script, Key Script, Core Script, Skeleton Script Body at the least) and that each one contains multiple modules, sometimes numbering more than a hundred.

Then consider that upgrading DMSI means I have to adjust, change, optimize, add to and/or replace some or all of each of those sections, with multiple modules each, usually having multiple statements each, without breaking inter-operability and inter-dependencies.

Finally, in DMSI, each statement can be pages of text long. So it's not exactly easy to work with them and maintain grammatic correctness. Even after all these years of doing this, I have to work on each statement in staggered sections that overlap to make sure the grammar is perfect.

And then you have the fact that I have a life, just like anyone else, and shit likes to happen to me.

So I had to build USLM3 and UMOP2 before working on DMSI 3.3 again, and that is done, and I spent the rest of today resting. I almost burned myself out trying to get all that done so fast.

Now I will resume working on DMSI 3.3, but I don't want to release it without having made enough improvements to it to be worth my time and yours. There is a lot left to do, so I'll be working hard, but setting deadlines when it's not absolutely necessary tends to result in dissapointment.

Of course I know there are some of you who think I'm silly for not using deadlines more often, but I know two things are true when it comes to deadlines.

First, they almost always result in less good quality than just working steadily until the job is done.

Second, I personally don't do well with deadlines.

So since you guys are waiting for something good, we might as well work on it right and do what it takes to get the best results we can get.

That said, I don't know when it will be finished; it might be on or about the 20th, still. Or it may be later. But for those of you who have a problem with it taking so long, I can only say that in my shoes you would be in the same position.

Doing it right is better than doing it fast. Complaints on this can be filed in the circular file. Working at my own pace, and in my own way, is how I achieve programs worth paying what we charge for them.

You guys are going to see what DMSI Final is like soon enough. It's not too terribly far off at this point. Especially with this cycle ending at the end of December. Maybe then, we can return to building it every couple of months.

I am definitely ready to be done with DMSI AND developing 6G!

@Shannon

Have you considered looking into some form of automation to help you reduce your workload? I think AutoIt might be a good place to start