Kees
|
Working with 4.0 for stand alone website.
- I insert a picture of 900 x 600 pixels.
- I scale it down to 150 x 100 pixels
- I put preview to YES
- In a preview when I click the image it shows the 150 x 100 pixel version instead of the 900 x 600 pixel version.
Sound familiar??
Support can't replicate the problem.
|
| |
Dave B
|
Going through the same exact issue. Support is saying that they are able to get that to work using my artx file.
Per their request I spent over an hour removing all of their programs and cleaning every trace from the hard drive and 40+ registry entries. Basically like a brand new install like a new customer and it still didn't work.
There is some weirdness to the whole thing. I am using the internal release 4.0.0.59100 and it isn't working on some existing projects I made with previous versions. New ones seem to work.
I believe that it's the internal releases that don't work. I reverted back to 58475 and they seem to be working now. Although I updated to the internal release to fix something else, now I can't remember what.
It is annoying when they say they can't reproduce the issue. I asked them to send me the exported project in a zip file for me to verify that. No word since then.
|
| |
Kees
|
I went through the same procedure with support.
deinstalled software
cleaned registry
erased roaming directories
reinstalled Artisteer
Still same problem.
I send support my artx file. They say they can't reproduce the problem. They send me screendump to prove. Very weird.
It all works fine in new projects, not in existing projects.
To be continued
|
| |
Tom
|
Lightbox doesn't work for me either either.
|
| |
Dave B
|
Like I said you can't use any new internal releases. I just got my exported project back from them and it was exported using v4.0.0.58475 which works.
Funny they told me they were using the latest internal release 59100. There is couple hours wasted.
It would be nice if they would not tell you to upgrade to a newer version to fix something then it doesn't and then they claim they are using that version and can't reproduce the problem. Then it turns out they are using a version that does work. I don't care to F with my computers registry. Not cool.
Why can't they release some updates, the official updates had so many bugs what does it matter.
I like this software, just frustrated with support.
|
| |
Josicus
|
I'm using the 4.0.0.59100 as well. It fixed the path for exported images and some other bugs as well.
So far, Artisteer support has always been very helpfull towards me. They offer me work-arounds, hints, or if needed an internal release. Thumbs up for that!
I suggest that if you need support from Artisteer that you write clearly the issue you have and provide steps how they can replicate your issue. And last but not least, watch your writing tone....
Software developers do not make a product to screw you over.
My 2 cents..
|
| |
Dave B
|
Quote :I suggest that if you need support from Artisteer that you write clearly the issue you have and provide steps how they can replicate your issue. And last but not least, watch your writing tone....
That's fine, but when they tell you that they can't replicate something and claim it is the same version you are using and spend 2 hours trying to fix it only to find out the support person can't even figure out what version they are using kind of brings out some tone. They asked me to go in an edit/remove registry entries. I am capable of that but still the margin of error is high and someone who doesn't know might try it and jack their machine up real good.
They told me to install the internal version 59100 to fix this but it doesn't work on existing projects only newly created ones (my case anyway).
That's all. I have good luck with support for the most part.
I also feel that using internal releases and reporting bugs for them to fix is a service to them. Beta testing is a valuable service and should be appreciated. Especially someone who has taken the time to learn the software and knows what it should be doing. Sometimes you spend more time trying to explain to them what is going on. The support ticket folks are NOT the developers by the way.
Bottom line is this whole thing could of been avoided with me by simply using the correct version on their part and saying yes we can replicate this and will pass it on to the developers. 15 minutes on both ends no harm no foul. Not the case this time.
My 2 cents..
|
| |
Tom
|
I'm using Artisteer.4.0.0.58475 and it does not work.
|
| |
richard
|
I formulated a php fix for the imported image path issue. East to implement.
http://www.artisteer.com/?post_id=207389&p=forum_post&topicsPage=3&forum_id=13
The link to the fix can be reached via above link. This will remedy the issue and free you from the additional bugs in the internal version. If that version was any good it would have been released...
|
| |
Dave B
|
Quote Tom:
I'm using Artisteer.4.0.0.58475 and it does not work.
Dumb question but are you inserting large image and sizing down with the preview set to yes?
|
| |
RTWright
|
Apparently some of you have never worked in the Software troubleshooting end of things with PC's. Every machine is totally different by design, every hardware configuration as well as software is different. We all have so many different kinds of PC's it is impossible for any Developer to even fathom just how many issues they're going to run in to.
I've been building computers a very long time, I've been in computer retail and support as well. They may very well be using the same version and not having any issues with it because they don't have the exact same software - hardware setup as you and I. So them replicating anything exactly is pure chance. Which is why it's VERY important to take notes, screenshots, full details about what you're doing.
I'd go as far as to say something could be causing this that isn't on their systems and is on yours. Since I don't see a ton of complaints here but hundreds of people having this issue, it seems rather isolated. That makes finding this bug even harder.
Now I do understand frustrations as I've had them myself and did my best to give information to companies before. But since they never put you in touch with the Developers directly? I'm more than certain that there is a broken line of communication that happens here.
|
| |
Dave B
|
This is an issue on 2 totally different computers for me. Hard to believe that's the problem here with a lightbox not exporting the large version of the image.
I too am a computer tech or whatever and you are correct some problem regarding the software are most likely related to that. I doubt the software's ability to create lightboxes is even remotely related to computer hardware/software. The freezing/crashing is almost certainly that. Anything related to stability is but not seen much in the way of software not doing what it is supposed to do because you don't have enough memory or a new processor if it meets the minimum requirements. Or I have been lucky for 12 years.
Development Environment
Intel or AMD processor 1500 MHz or higher
150 Mb free disk space
1 Gb RAM or higher
Microsoft Windows XP, Vista, Windows 7, Windows 8
Microsoft .NET Framework 3.5. It can be obtained from the Microsoft website at: http://www.microsoft.com/en-us/download/details.aspx?id=21
Again, I have problems with only certain projects using the internal release 59100. So it's a program issue not a computer issue or none/all would work. When I revert back to the older version that problem goes away.
|
| |
Tom
|
Quote Dave B:
Quote Tom:
I'm using Artisteer.4.0.0.58475 and it does not work.
Dumb question but are you inserting large image and sizing down with the preview set to yes?
Yes I am.
|
| |
Tom
|
@RTWright
I have been a software developer and IT Tech long enough to know that the problem is always either your hardware, some other software conflicting, or you have malware - it's never our product or service. ;)
|
| |
Dave B
|
To be fair, support has almost always eventually recognized and admitted the problem. I have been told a couple things that I did not care to hear.
I just received notice that they have replicated my issue and are passing it to the developers.
Man they have a lot to fix.
|
| |