Design problems

T Qih
13 years 152 days ago

When i set the number of designers it gives me one date for the next model, then I save it.
When I get back to the design space to check, it gives me another date for the next model.

For an example:
I set 17 designers and it gives me day 26 for next model, after saving I come back and it's for day 27.
If I set 20 designers it gives me day 26 for next model, after saving, when I come back it's for the day 27, if I change for 19 designers it says that next model will come in day 26, but after I save I lost that.

Is it a bug?

Unknown
13 years 152 days ago

Had a similar problem today, only after increasing number of designers by one, and then decreasing it back, I got one more day before design is ready. And if I refresh page (without saving), I get one day shorter design again.

T Qih
13 years 152 days ago

I did that too, but nothing that I try to make it right works...

Jake Goodhall
13 years 152 days ago

I tried to make this happen in my design page but it only gave me the same values as before - I could not emulate the problem.
Can anyone else do this?
It might help Jack find the problem.

T Qih
13 years 152 days ago

what do you mean with "emulate the problem" ?

Jake Goodhall
13 years 152 days ago

I couldn't copy what happened to you.
The same thing did not happen to me.

Carlos Santos
13 years 152 days ago

"Eric

I tried and this was happening to me too, however, before posting here, I decided to make sure that I was right and went to double check and it wasn't happen anymore?! I'm confused lol maybe I'm too tired...

T Qih
13 years 152 days ago

The image above shows my problem.

The first one is when I open my design, the next model of sidepods will be ready in 27 Jan.
On the second I set the number of sidepods designers from 17 to 16.
After that I raised it again to 17, and the next model day upgrades to 26 Jan with the same 17 designers of some other components.
The last one is after I save, the day model get back to 27 Jan.

Hope it can help the developers to solve this.

Gyuri VanLittas
13 years 147 days ago

Maybe becauce the day you set it was 26th already and the days development already over

Jack Basford

CEO & CTO
13 years 146 days ago (edited 13 years 146 days ago)

This has been a known issue for a while. I investigated it a few weeks ago but was unable to get to the problem, despite going through the code several times over. I am pretty much certain that it is a discrepency between the calculations JavaScript is doing (when you change it dynamically) and the calculations PHP does (when you refresh the page after saving it). Though it is fundamentally identical code.

Thankfully it is very rare and quite insignificant in the grand scheme of things, so I've been able to use my time on more important issues, but this still nags me. I'll get to the bottom of it for the Q1 patch.

Edit: Thanks for the screenshot.

Andrew Hurn
13 years 146 days ago

Should there be a list of known issues?

Jake Goodhall
13 years 146 days ago

Yeh That is a good idea - then people won't keep bringing up the same problems after it has been discussed.
The Q1 patch & survey thread should highlight some of these problem though

K Huisinga
11 years 98 days ago

I'm not sure what the status of the patch is, but I am currently having the exact same issue, and have been for about a week. I had it once before, but it went away after a while - do not know the conditions were to kake it go away. Wish I did, I'm currently 2 days from producing a new model, regardless of how many people I throw at a component.

Nick Gatto
11 years 97 days ago

This post was from 2 years ago, I believe the patch has already been released :).

Also, there is a minimun dev time of 2 days, so no need to add any devs beyond that

Profile

Notifications

No Unread Notifications

Design problems