tinkergnome 927
45 minutes ago, Shadowman said:And to clarify the owner of Cura; it is Ultimaker.
Also just to clarify:
The 'product owner' is a role in agile software development, in this case probably just a different person (not mentioned by name) that is working for the company though. At least we know that it's not Marco...
Not every employee of Ultimaker is active on this forum, it's meant as a forum for the community, not as a support forum of the manufacturer. The best way is indeed to bother your reseller with those problems (the more the better...). The network of resellers (pun ?) is the "voice of the customer" the product owner is responsible for. ?
Edit:
It doesn't hurt to mention issues here on the forum though - but this voice is far less powerful... ?
Edited by tinkergnome
Recommended Posts
Dim3nsioneer 558
It's a bug in Cura, Cura Connect and the Ultimaker app. I thought it would be fixed with Cura 3.5 but obviously that fix takes a bit longer. Maybe @Marco_TvM can give us an update on this?
Link to post
Share on other sites
Marco_TvM 34
Hi Dim3nsioneer,
I'm afraid I can't answer that. The only one who can is the Product Owner of Cura.
Link to post
Share on other sites
Shadowman 53
You likely know this and yet;
When connected to your internal network your IP address will be input as shared; 192.xxxx however, if connecting outside of your network your IP adddress input will be your Public IP such as 127.xxxx
When accessing using your Public IP address you need to Port forward 8080 within your router to the printer’s internal IP address.
And to clarify the owner of Cura; it is Ultimaker.
Link to post
Share on other sites