I'm currently working on (free) updates of my Poser tools, mainly Poser File Editor, Poser File Organizer, and Runtime Repair/ZIP. Please let me know if you have any suggestions for improvements or new features to include in the updates, or if there are any bugs or other problems that need to be fixed. You can either reply to this topic or send me a site mail.

I like Poser File Editor very much, mainly using it for Poser file examination but also for editing on occasion - it is set as my 'External Program' for interPoser Pro content and scenes :).  What I'd like to see is a multi-document style so that manual comparisons between two files can be done (tile vertically or similar) or just being able to load several files into a single running instance of PFE.

I have had a crash or two loading some of the more esoteric CR2 files.  Can't tell you which ones offhand but if I happen upon them again, I'll be sure to send you more information.

Robert

I agree with Kuroyume's multi-document request: one of PFE's main uses for me is copying stuff from one file to another. On that same task, having the keyboard shortcuts ctrl-C, ctrl-X and ctrl-V available would also be useful.

About the multi-document feature, I don't see the advantage compared to just running several instances of Poser File Editor. It's no heavy-weight application that consumes many system resources or takes long time to start.

About files that cause a crash when loading, if you can send me the file, I can examine it.

About keyboard shortcuts, consider it to be done.

Tongue in check and one can wish....but I and a lot of others would buy Intel Mac versions of all your products. Having to flip back and forth to windows is a royal pain, let along having to deal with network drives, etc, which a lot of poser tools don't support. If win is it, then please don't make the program look for a resident version of poser on the win side to be able to work. That is a deal breaker for us mac users that emulate windows.

Since I don't own a Mac and never programmed for Mac, it's rather unlikely that there will be Mac versions of my software. However, if there are any particular problems when using my tools when emulating Windows on a Mac, please let me know so I can try to avoid them.

how about a tool for moving a product from runtime to runtime?

I very enthusiastically endorse Khai's suggestion. The added ability to delete a product and all it's various supporting files would be great as well.

Here's one that isn't too difficult and would be very useful - to me anyway. ;)

When you save an existing file as a new file, have an option to copy the thumbnail image from the existing file as well.  There are many times when I edit a CR2 where I don't want to alter the original so I save as a new CR2 but the thumbnail doesn't go along with it.  Not a big deal but would be a nice convenience.  This should simply be a matter of checking for the existence of a matching .rsr and .png file for the original CR2, copying, and renaming them to the new CR2.  Normally, I do this manually.

yeah a tool which you can select library files and move or delete them along with all of the supporting files would be extremely useful. I too would add my vote to a two pane PFE, yes I can open up two versions but its much more conveniant to have two panes side by side in the same window as I dont have to move and adjust the two copies each time I open the software, and I use a two pane view so much that I tend to use cr2 builder more than your excellent product even though I like your features a lot more.

Khai, kalon, wdupre: Poser File Organizer has a feature to move or copy Poser files together with thumbnails and all referred files (or referred files of selected types) to a different Runtime. I did not include a delete feature, because it's more safe to move the files to an empty Runtime and delete them there. (Some products refer to standard Poser content, which should not be deleted.) While it would be easy to implement a delete feature, usage would be at user's risk.

kuroyume: An option to copy the thumbnails sounds simple and useful, I'll put it on the list.

wdupre: Poser File Editor already remembers the position of up to 10 instances, no need to always move them side by side. The reason why I try to resist a multi-document support is that it is rather lot of work for only few benefit.

Oops :blushing: nevermind, I have never even looked at PFO

Quote - Since I don't own a Mac and never programmed for Mac, it's rather unlikely that there will be Mac versions of my software. However, if there are any particular problems when using my tools when emulating Windows on a Mac, please let me know so I can try to avoid them.

My last comment is key. If us Mac users are running win via boot camp or parrelles please don't have any app you design require that it check for a valid copy of poser or DS on that side of things. I for one don't want to buy two copies of poser just to use a tool on the win side. FYI, there are tools out there that unless they can find a valid copy of poser on the win side, they will not function. Some don't do network drives also. In the later cases it's a pain but I can create a false or temp runtime and copy files and folders back and forth. But it is a step I would rather not have to deal with or nor drive space I don't want to take up with duplicate files.

Thanks for listening. The first comment about programming for mac's was bit of  tongue and cheek humor.

My Poser tools don't rely on any external programs or data. The only exception is the file "LibraryPrefs.xml" with the external Poser Runtime folders that should be located in the prefs folder of the main Poser Runtime. Otherwise, the tools are restricted to a single Runtime folder.

If you like, you can try the demo versions of Poser File Editor and Poser File Organizer to find out how they run on a Mac with emulated Windows.

Okay, I too did not have Poser File Organizer, so I got it yesterday.

Handy little program. I'm still getting used to it, so I may have missed something, but I have two requests and a question.

It would be nice if you could favorite your runtimes, instead of having to climb/descend the tree in the browser and two, it would be great if it could remember the last folder you visited instead of defaulting to the Poser (exe) runtime.

As for my question...
I see that if I chose, for instance a CR2 to move, PFO will move the CR2, OBJ and any texture maps associated with the CR2. If I move a mat pose file, from what I've seen PFO will attempt to resolve the path to point to the runtime I'm moving the mat file from. Is this correct?

If it is correct, is there any way that PFO could move the mat file and pull the textures with it to the new runtime.

I'm trying to close down a runtime, only everything is not being moved to the same runtime. I need all of the files, whether they're extra textures (not called by the CR2/PP2 or HR2), morphs etc to be moved.

About favorites for Runtimes, you can define and save your own lists of files and folders (including Runtimes) in the file tab. Isn't this a kind of favorites? You can even define one list with all your favorites and then select which one to process.

Remembering the last folder should be not much work, I'll put it on the list.

I'm not sure about your question. There should be no difference whether you move a CR2 or a mat pose file. In both cases, all references will be moved as well. If "same runtime only" is checked, only references located in the same Runtime are moved, otherwise references from any Runtime. Of course, referred files are not moved, if they are already in the target Runtime, e.g. because they are used by other files that were moved before.

I'm using the move option on all content during installation, and never missed a file. (But it's interesting how many products contain files that are not used by any of the included Poser files.)

Sorry, you're right the textures are being moved. The OBJ and PMD in the same folder are not... am I missing a switch?

I would love if rather than choosing to have PFO search for referenced files either only in the same runtime as the content or all other runtimes I could set it to look in a specific runtime(s) of my choice. My own set up is all my geometry textures are in the main runtime and the content that calls them are in seperate "theme" runtimes. I tried to use PFO to move the geometries and textures out to the themed runtime but because of all the duplicate file naming and such the result was a total mess of lost references and I had to re-consolodate all the textures and geometry back in the main runtime.

Fancy choices I would love in PFO are:

1. To be able to choose to have PFO move .obj files from the libraries folders to the Geometry Folder and to integrate .pmd files into the .cr2s. Right now my EF character .obj and .pmd locations are totally screwing up my library directory structure.
2. To relocate Injection/REM files to a new Injection Folder since content developers have spread their INJ files in folders all over my runtime making a terrible mess.
3. More fun stuff would be to be able to move FBMs from one figure to another taking the required morph channels. Basically to add some morph channel editting features, esp, if they retained the Poser dial grouping since MorphManager unravels dial grouping.
4. To be able to strip all texture refences from a .cr2 or .pp2.
5. To be able to set to a certain surface color and/or ambient color to all materials on a figure or prop.
6. Dream Feature! To automate setting up alternate MATposes to a new texture folder containing copies of the textures sampled down to a lower resolution.

Also, if I recall PFO now gives an error for texture "NO MAP" or whatever the null setting is in textures.

Apart from PFO what I really want is Explorer style UI to load content from the runtimes... something like ockham's free Loader.py with directory trees but with a thumbnail view of the content and even beter a search feature.

Really I would love a comprehensive Poser GUI replacement like the old UI .py that used to be around in Freestuff... I miss the old Poser 2 interface and would prefer a simple tabbed interface for Poser with maybe sliders or "+" and "-" button controls rather than dials to replace the terrible "artsy" space-taking interface Poser 3-7 have but I don't see I am ever gonna get that.

Quote - Sorry, you're right the textures are being moved. The OBJ and PMD in the same folder are not... am I missing a switch?

You can select which types of file references to move/copy and which not. The default is OBJ, PMD, and Texture. In addition, you can include Poser and Python scripts. If there is a correct reference to a file, it should be moved. Otherwise, there should be an error log message, either that the file was not found or could not be moved.

Quote - It would be nicer to correct missing file references electively after the file run.

I will consider an option to postpone searching for missing files (like Runtime Repair is doing), but I'm not sure whether this will be possible without changing the processing flow of Poser File Organizer.

Quote - I would love if rather than choosing to have PFO search for referenced files either only in the same runtime as the content or all other runtimes I could set it to look in a specific runtime(s) of my choice.

While not impossible in principle, it's difficult to provide an easy way to configure this. Maybe textures are in one Runtime, geometries in another, INJ poses again somewhere else. I will consider it, but I'm not sure about this.

Quote - Fancy choices I would love in PFO are

1. A. Moving OBJ/PMD files from libraries to the geometries folder would be a reasonable feature, I'll put it on the list. By the way, Runtime ZIP already has a feature to do this when extracting Poser products.
2. B. If you want to convert PMD morphs to embedded morphs, this is one of the features of Binary Morph Converter. Hence I won't include it in Poser File Organizer. Poser File Editor also can do this, but for single files only.
3. There's nothing to tell an INJ/REM pose from other poses for sure. I don't think a task like this can be automated. However, just moving the files manually to a new folder and then let Poser File Organizer fix the references could be an option.
4. This can be done in a few steps with Poser File Editor: Isolate the morphs/groups in one CR2 and then import them into the other CR2.
5. I don't think that this is a feature for a batch processor, because it can cause a lot of damage. However, with Poser File Editor or Tool Collection for Poser, you can easily remove any file references from a single file. (Before, you can save the material as a mat pose in case you want to apply it again.)
6. Outside of Poser, again something that can be done with Poser File Editor. Inside of Poser, there is a Python script included in D3D Pythons 1: Material Utilities that can do this.
7. This would require image processing. While it would not be too difficult, I doubt that there is much need for a feature like this.

Quote - Also, if I recall PFO now gives an error for texture "NO MAP" or whatever the null setting is in textures.

Poser File Organizer accepts only NO_MAP and :NO_MAP for no texture, but misspellings are not rare. These are handled as invalid references. Just replace them by no file, and it will be set to NO_MAP.

Quote - Apart from PFO what I really want is Explorer style UI to load content from the runtimes.

Apart from the content library, I could list dozens of UI improvements that should be done for Poser. But I guess using DAZ Studio or hoping for Poser 8 are the real options here.

With respect to empty texture map references, there seems to be at least four possibilities:

NO_MAP
:NO_MAP
"NO_MAP"
":NO_MAP"

I'm so glad that the developers were decisive about a clean, singular format...

I've seen the "NO_MAP" variations cause problems with some items.  Poser (on some machines) appears to be looking for a file called "NO_MAP" -- which file of course does not exist.  Upon attempting a render, Poser will chug for awhile and then issue a warning dialog which states that "The File was not found" -- without specifying which file wasn't found.

I've recently purchased Runtime Repair, but I haven't had the time to install and use it yet.  I'm looking forward to using it -- especially on old products and runtimes.

The currently released versions of Poser File Organizer and Runtime Repair only accept NO_MAP and "NO_MAP". Runtime Repair has an option to correct misspellings like NOMAP and NO_MAT, also with additional colon.

The upcoming versions will both have an improved feature to fix irregular uses of NO_MAP for maps or "" for files in image nodes.

Actually, the most annoying thing about file references in Poser 7 is that the path is missing for images that are used in the shader tree, but not in the P4 material settings. Even when the MAT pose was applied correctly, the file reference will not work when reloading a saved scene.