If you need to use RTEncoder for a product to work would you hesitate to buy that product?
Yes or no will do.

No! :)

no hesitation here!

Yes, I probably wouldn't buy the product - in fact I've avoided buying at least one product for that reason. The seller assumes you know what an RTEncoder is, where to get it, how to use it. Since I don't know any of that, I don't buy.

No hesitation unless there was some doubt that I had the correct version of the encoding item.

No hesitation.

LindaB cant be the only rosity member unfamiliar with Objaction Mover and/or RTEncoder, so Id say her concern bears focusing on.

Id think the easy solution would be on the products description page, to clearly state RTE is required, boldly proclaim its free, give the download URL to RTE, and possibly even include a URL to an RTE tute (if there is one, the instructions in RTE's ReadMe has always been clear and sufficient as far as ive seen)

Proclamation of the freeness of RTE and the download URL in the product ReadMe is prob a great idea as well, although you may need to get a permit from the Department of Redundancy Department.

Yes. I have heard it is difficult to get an RTE encoder working on a Mac. Furthermore, encoding presumes that at least some of the mesh is not original. That makes it at the least duplicative, and very possibly non-optimized. Not the first thing I look for in a mesh.

no

No hesitation here. 

I once was a yes, but now i'm a no.

when i was a yes it was for the same reasons that LindaB has stated.

If the ad would give a brief description of what RTE encoding is and why it is done, think it would have swayed me sooner.

No.

But I was a yes until a product came along that I simply  had to have. Had I realized how easy it was, would not have worried. 

Not anymore, but when I was newer to Poser, yes.  What I would appreciate is the merchant at least include a link to the program instead of just saying "use objaction mover".  Heck, I had to post here asking what that was and where to get it.  LOL  A link would have helped big time.

Another "no" before, but "yes" now. And it was no for my first 3 years of poser use.

I'd avoid it if possible, but that's not always practical.

I'm with Acadia: if the product vendor has been smart and/or kind enough to include links to the necessary software to decode the mesh, I don't have a problem with it at all. The biggest failing I see with products, encoded and non-encoded, is sparse documentation that assumes a depth of knowledge on the buyer's part, or that the buyer has all of the necessary utilities to prepare the product for use. Clear documentation will overcome most objections I might have to a product, and that includes accurate links (and correct e-mails for the vendors, in case we need to contact them for support).

Yes .. I would hesitate because it isn't really available for Mac at this time.

To my own surprise it can be done in Mac. I found that if works if you use the 1.01 version of RTEncoder to encode the file. It then can be decoded in Mac with RTEJava 0.5b

Now it is in the hands of the merchants to update their encoded files (like me for instance)

Was once "yes" before I knew how easy it was. Now it's a loud "NO." RTEncoder is SO easy to use. Unfortunately, many of the read me's make it sound complicated, when it's as simple as "point and click," "point and click,"  "save as." 

But for a newbie, everything Poser sounds so complicated.

-- Jeff

There are Poser tutorials here at R. Get an encoder tut on there, with a very clear why it has to be used, and a step by step example of how to do it. Provide link etc, and every vendor can refer to that tut.

That's the function of the tutorials section here. Not endless ways to hide limits of the renderer (app and person) by doing postwork.

I've optimized all my meshes using Poser File Organizer in order to save memory. RTEncoder will no longer work on them, so I'd never buy anything using it.

Thank you everybody for your inputs and good suggestions!

I think I'll do a step by step with pictures and link to it on the product page. That way one can get a good idea how to go about before buying. And also I'd make sure there would be proper links (and working) for the encoders.

There is a version 2.0 (something) BETA of the RTEncoder being tested for cross platform use. Hopefully it will be done and released soon.

Again, thanks everybody!

Using a Mac with OSX I've had a problem with two obj-files: the House-Mouse from DAZ and Jessi in Poser 6. The obj-files of the House Mouse are different between Mac and PC, IIRC there are extra line-feeds in the Mac version and that is enough to prevent RTEJava from working. As I have a PC also I tried to decode the stuff with RTEEncoder and it didn't work either. I don't remember exactly what the problem was with Jessi, but I think it was that the time-stamp is different between the Mac and PC versions, and that RTEEncoder didn't work here either with the Mac version of Jessi. Edited to add that no, I wouldn't hesitate as long as I am sure I have the correct source-file.

Quote - The obj-files of the House Mouse are different between Mac and PC....

Hmmm... good to know.  In this case it is the Mildog. So the only way to know if it'd work or not is to test on Mac? Or is there another way?

No, it is imo very easy to use. :-)

Quote - > Quote - The obj-files of the House Mouse are different between Mac and PC....

Hmmm... good to know.  In this case it is the Mildog. So the only way to know if it'd work or not is to test on Mac? Or is there another way?

I don't know if it is the only way, but it certainly sounds as the safest. Although I wonder if you could download the installation file for the mac from DAZ, expand it with winrar, and open it in a text utility to check, and/or use it for encoding.

PS Does this mean that we're closer to getting those wonderful furry dogs of yours? YAY!

I have the Mil Dog so I could download the pc-version as well and try it out, if you like. I could encode something on the pc with the pc-version and then try to decode it on the Mac.

The biggest problem with purchasing RTEncoded content is that it only works on a specific version of the figure. I don't know if RTE is less sensitive to figure versions than Objaction Mover (which won't work if just the date is changed in the file), but I've run into some content that requires finding an older version of a figure to correclty work, requiring some trial and error to find which one works. That then sticks the purchaser to figure out how to transfer that content to the most recent version of the figure.

I have to check RTE Java again but I don't think it worked the last few times I tried it.

No.

Quote - PS Does this mean that we're closer to getting those wonderful furry dogs of yours? YAY!

Dogs coming along fine.
May sell through Renderosity (if they'll accept it) instead of DAZ, that is why I wanted to know what everybody thinks of the encoders.

Quote - The biggest problem with purchasing RTEncoded content is that it only works on a specific version of the figure.....

Didn't know that. :ohmy:  How do one solve that issue? I hope it is possible to release it with encoder so it doesn't give too much hassle to everyone. 

I really appreciate the inputs on this, thank you everybody. I will get back with you all for advice and "test help"  when it is closer to release.

Always been one of the no mob as far as this issue is concerned.
I first started using rtencoder & objaction mover with freestuff, so when I started buying items, I was already familiar with how to use these two programs, and I have them both installed on my PC..

The only thing that would stop me buying an rtencoded product would be if I'd not got the required item that the product had be encoded against.

Other things being equal, I prefer a model that comes with

its own OBJ.  I've had problems making RTEncoder work right.

However, your stuff is so good that 'other things' are not equal! 

Yes, wouldn't buy.

Depends on how bad I want it..

but if it isn't totally amazing.. I wouldn't bother buying it

Quote - Using a Mac with OSX I've had a problem with two obj-files: the House-Mouse from DAZ and Jessi in Poser 6. The obj-files of the House Mouse are different between Mac and PC, IIRC there are extra line-feeds in the Mac version and that is enough to prevent RTEJava from working. As I have a PC also I tried to decode the stuff with RTEEncoder and it didn't work either. I don't remember exactly what the problem was with Jessi, but I think it was that the time-stamp is different between the Mac and PC versions, and that RTEEncoder didn't work here either with the Mac version of Jessi. Edited to add that no, I wouldn't hesitate as long as I am sure I have the correct source-file.

DAZ seem to have a habit of making changes to OBJ files which break them as keys for RTE-encodes. Apart from the PC/Mac difference (The PC textfile standard uses a 2-character EOL-marker, the Mac only one), the copyright-notice comment has changed with every revision to V3. And that's the only change to the OBJ file. I'm not sure that they even realise they're doing it. I've hit this problem a few times, on purchased stuff and freebies, and merchants need to be careful which version of the keyfile they've used. And I have nothing but praise for the responses I've had when I've contacted the content-creators involved.

no, but with a codicil.  it matters a) what it's encoded to and b) the customer support history of the merchant.  i don't think the mill dog ever had an update.  so it's probably a no-brainer to decode with.  decoding withv3, m3, aiko and others - big pain because there's so many different versions.  and in the case of the former, multiple products are involved.    also, you have a history of excellent customer support.  people who release a product, but never post to the threads where people ask questions about it, i wouldn't take a chance on.  because if decoding _didn't _ work, i'd want someone to work with me. 

and i think your stuff is "totally amazing".  i've never forgotten that avatar of little dragon's, the walking black cat with swaying hair.  one of the best advertisements for your cat ever.

I was so happy to get rid of the RTEncoding on Glamorous Jessi.  ;-)

Yes, there are at least 3 versions of the Jessi OBJ (or OBZ).

Quote - If you need to use RTEncoder for a product to work would you hesitate to buy that product?
Yes or no will do.

Yes. I would almost never buy an RTEncoded product.

It's a serious pain in the behind. Not jsut the issue of the initial install - but the inevitable breakage as product updates and so on happen. Why would I let myself infor another level of worry in an already ridiculously bad situation (Poser content updating)?

Maybe.  It does get a little tricky. 

I've jumped through some vendor's hoops to un-encode their products ( and they don't always ask you to point at an OBJ file to do so !  RTEncoder just needs you to have a specified file to check against ).
So far so good, so I'd have to say YES.

Yes, I would hesitate.  I've had some bad experiences with RTEncoder, too.  If it was something I really wanted then I would still get it and hope the ReadMe file had good instructions on which source file to use and where to save the new OBJ file.  I have the furry kitty and I can't wait for a fuzzy doggy to chase it.

Maybe if it is easy to use. Otherwise no

I'm replying to this old thread for the sake of those who may search the forum in the future.
I'm the author of the free RTEJava utility. RTEJava works on both Windows (95 and later) and Mac OS (8.1 and later, including Mac OS X).
I built RTEJava for myself to use on my Mac. RTEJava is not perfect, however RTEJava works!!!
RTEJava is a Java application, so it may work in some ways that are unexpected if you have used only native Windows or Mac OS applications in the past.
If RTEJava won't launch at all:

• Ensure that Java is installed correctly. Refer to the included READ_ME.HTM file located in the Documents subfolder.
• Mac OS 8 or 9 users need to ensure that Swing is installed correctly, too. Refer to the included READ_ME.HTM file.

If you encounter a problem when choosing the key file while decoding a rte file: - The name of the key file appears in the FileChooser dialog as a HINT only: You must navigate to the folder that contains the key file you want to use and click on it to actually choose the key file.

If you encounter any other problems while RTEJava is running: - Click the About button to get information about your OS and Java version, along with the RTEJava bug report e-mail address.

• Write an e-mail (English only, please), explicitly mentioning any error messages that RTEJava displayed, and the OS and Java version shown in the About box.
• Send the e-mail to the RTEJava bug report e-mail address shown in the About box.

Don't hesitate to use the RTEJava bug report e-mail address: I can't improve RTEJava if I don't know what problems folks are having!

Yes.  I have RTEncoder, and I know how to use it.  It's just an extra hoop to jump through, and I'm lazy.  :-)

If it's something I really, really want, I wouldn't hesitate.  If it's something borderline, though, I might pass. 

I am very lazy, however.  I own Wardrobe Wizard and still buy multiple versions of the same outfit sometimes, because I'm too lazy to convert them.

I have hesitated in the past and have had issues due to having the wrong version of the obj file as well as it being an extra step that I'd rather not have to do.

I'd like something that works across all versions and also has an automated setup so I don't have to look for anything.

Yes. Even though I know how to use it and have used it on a handful of "must-have" items like Glamorous Jessi. Because it demands a specific version of the purchased item, it's a PIA to use. For example, I don't have a clue which V3 I have and I don't care. Until I see something that requires RTEncoder and V3SAE, whateverthehell that is.

In the specific case of the MalDog, I'm very aware of its "Fixed this. Oops. Fixed that. Oops!" history (which ended, in my view, somewhat the same way the Republicans ended the Viet Nam War: Declare victory and run for the helicopters). I would assume that if I need RTEncoder, I will also end up needing some version of the dog that I didn't pick up or can't find.

I don't resent having to use it, and I use it when I have to, but I don't just shrug when I see that it is required. I feel kind of the same way I do about buying furniture that needs assembling. Wary of the unforeseen. It adds one more thing that can go wrong, and I've seen it go wrong.

M

I'd say "NO"..but only on the proviso that all the relevant info is PLAINLY available to the purchaser BEFORE  purchasing....explaining exactly WHICH files are needed to get a succcessful outcome.

I will mention, get permission to release such a product. I think DAZ likes to okay these things.

Yes. Even though I find it easy to decode the files, I would not buy a product that requires decoding unless the merchant states very clearly that if it doesn't work for me, I'll be reimbursed. Reason for that is that I can't be sure the object I have is the exact same version as the one used to encode the files.

An example of that is Victoria 3: how many different versions of that object do we have? I lost count!
But it's not the only one. (A3,M3,V2,Mil "anything", etc.)

I have used it and objaction as well, but what worries me is aren't those programs owned by someone and if they pull their permission to use them for any reason are we out of luck if we don't have a copy? I also agree with the above, there are new users coming in every day who don't know where to find objaction and rte it should be clear in the ad what they are and where to find them.  No you don't have to do this but it is common courtesy and would probably get more folks to buy.

Hell no........  When I buy a car I don't expect the dealer to tell me that I need to get a free engine somewhere else and then figure out how to install it.  The item at the "other" Roc'ity is very expensive and for that kind of money I will not buy it as long is it is imcomplete.  To me it shows a contempt by the author towards his market.