Nice !!

And, thanks for freebies' link. I'll check them out tomorrow.

Thank you for your comments !

Problems ? With the auto-save ?? Um, yes, I've a fairly fast AMD system with 8 cores & 32 GB RAM, but saving scenes in PP11 is a lot slower than I'd hoped.

Doesn't help that my twin GPU cards can't multi-task. If I want to do do 'other stuff', I must render using CPU, as that has cores to spare...

Hmm. Will PP render in background using GPUs ? They're both GTX 750 Ti, should be able to support 'people speed' stuff as well as rendering. Unless they don't, but scant clue in the manual. At least, nothing I can FIND....

( US manual, US 'sort the headings' index. But, unless you know the manual so well you don't need the index, you don't know what to hunt... )

OT: Really annoying that Poser manual has so many gaps and 'hand waves'. Perhaps now Renderosity has taken over, more info will be added. And index / search key-words padded out, so a search for eg light emitters or extreme ambient values would actually find something useful, rather than yet-another two-line hand-wave.

And rigging ?? I've recently dug back along my shelves, found several Poser 7 books I'd forgotten about. They actually make sense, unlike PP manual's 'one approach fits all'... ( I did a lot with P4, had bought but not installed P7, when a spate of dire HDD crashes plus unexpected 'family matters' took me out of CAD etc for a decade... )

Sorry for mutterings, I get so exasperated, and my 'must figure this' list keeps growing... Nik

Took another 4~~5 hours before I managed to sorta re-create this render, though the models were right there on screen.

My best guess seems to be for the lights' D/H/A to be pale blue, with reflection to multiply by lights, not object colour. Dial 'Advanced' default ambiance value of one (1) unto 50~~99, then render with Superfly.

One snag is a lot of material menu values seem to mutate when your back is turned. Another, renders are 'noisy', so I had to double the 'pixel' count...

I learned to render 'progressive', to allow me to cancel early if no lights within...

There's probably three better ways to do it !!

Thank you all. You've helped me towards illuminating a SciFi scene with a $$ Vanishing Point 'Maintenance Tube' set that has 'light panels'. Upside, now they sorta work, iteration required. Downside, I was a _tad _exasperated before any test-render looked hopeful-- And ONLY in Superfly !!

Also, you gave me the incentive to poke about in Materials' 'Advanced' parameters...

PP_11.3 Care: If you dial any parameter up to 'silly' in 'Advanced', save scene before you render, okay ?

"First, I couldn't find the light switch. Now, I'm getting a tan !!"

@4385975 https://www.renderosity.com/mod/forumpro/?thread_id=2935477&page_number=11

I've a 'running rant' about FBX imports on the 'wish list' thread. Here's the short version... First, find an appropriate import scale, which may vary from ~0.5 ~~3500 %. A very, very few FBX models are **correctly **rigged, load like it says on the tin. Posing them is non-trivial, but can be done without re-rigging. Some are 'welded solid' like an OBJ prop. Some arrive as a jumbled heap, per your example above. Some arrive as a flock of free-flying parts, must be parented to a 'place-holder'...

Oh, and if textures etc do not auto-load, there's no obvious way to aim Poser at FBX's associated texture directory per eg 3D Paint and say, 'There you go'. Hand-loading 50+ materials' texture maps etc is a total pain. I've resorted to exporting FBX files as ASCII from AutoDesk's free FBX toolkit, just to get a plain-text listing...

https://www.deviantart.com/nik-2213/art/FBX-and-a-D-uh-moment-837842799

#Bakensobek said... "I know native support for DS items may be wishful thinking, but if not so, an easy way to import them would be great."

IIRC, DAZ recommends crafting PCF files and using DSON importer. Perhaps I'm getting too old, but I've yet to make this route work.

I have imported a bunch of DUF/DSF props by converting them to OBJ/MTL using ($$) dsf Tools. Fixing their textures can be a bit of an adventure. And, yes, given I use OBJ/MTL models in several 3D applications,I'd like a utility to rip MC5/MC6 to MTL. Before my tree-pollen hay-fever struck, I'd begun to figure the mapping. Sadly, my anti-histamines' 'zonk' thwarted progress...

Poser UI has its woes, many probably due neglect by SM (*), but I find DS' UI inpenetrable. It's a bit like Unity etc in that you mostly gotta do stuff a very, very specific way. Worse, its library system really, really does not like 3rd-party freebies. Again, when my hay-fever eases, I'll have yet another try at mastering the 'DS Library' tutorial I found...

*) If you look back along this mega-thread, I mention a bug that's been around since P4: When imported OBJ calls for a missing texture, half the file name sought lies off the left of the field. Good luck finding that !! Probably a legacy from 8-character names but, hey... FWIW, to date, FBX import doesn't even offer such a browse option, or scaling to character, iteration required...

Thank you. I'll have another try...

Thank you. I've had similar issues while trying to convert props from DUF/DSF format to Poser that are too complex to figure via dsf Tools.

Poser, you can usually drag/drop PP2, CR2 etc directly into scene from an external folder, and the program cheerfully prompts to browse for textures etc. Try that with a DUF in DS, it just lists the missing files, offers no route to locate them.And such teeny, tiny print, too...

IMHO,Compared with the simplicity of Poser's 'External Directories', which can be anywhere in your PC or 'drive mapped' local network, DS Manual Install is so unfriendly, I must wonder if Daz is trying to hobble 3rd party products and move to an 'Apple' model...

Was okay until I re-imported a big FBX file to check scaling, then UI stopped responding and GPU went to ~55%, required hard exit.

Imported same FBX previously saved parented to dummy character. Similar but not identical sequence ensued.

Log shows nothing beyond the standard commands.

FWIW, I've even 'killed' the main-camera animation sequence lest that was responsible. No joy, not a clue. Ideas welcome, even on a '4x2'... ==

My current nemesis is a $3 budget robot from CG Trader. The FBX model (version 3) is hi-poly, high parts count, but not fully rigged. FBX is ~13 MB, imports inverted at ~1% scaling, requires parenting and 180º flip. Library CR2 ~48 MB. Loading one requires ~1 GB. Two plus LaFemme ~ 1.7 GB.

If Poser 'plays nice', superfly render with non-optimal lights but 24 pixel samples and 'progressive' gave

Ha ! Deleted both robots from scene. Reloaded one, side-shifted, loaded second. Lock-up and view-drift ensued, RAM usage soaring to ~1.9 GB before dust settled. Which is ~200 MB more than prior. A third loaded eventually, without camera drift, but taking P to ~2.5 GB. Fourth needed less RAM, 4@ + LaFemme ~ 1.1 GB total. Which makes no sense to me...

Thank you. Took a while to find 'morph targets' checkbox in settings, but done. Have searched and found log, so now I know where it lives. Next time there's a hang-up, will look there.

Tangential, 3D modelling programs have wildly differing ideas of import / export sign & axis conventions. A few small examples...

MMD PMD & PMX files may be exported, un-rigged, as OBJ/MTL from PMX Editor. But you must 'mirror' the model first, as otherwise appears swapped L/R. This may also confuse texturing...

FBX files may import 'on their face' facing 'forwards' or 'right'. This is after you've found an import scaling to get them on screen, of course, of course, ranging from ~0.5% to ~3500%...

And another import grumble. 'Features' Says PoserPro can import/export Z-Brush, but digging into documentation shows only compatible with GoZ files. Will not recognise or import ZTL models... { Mutter, mutter, mutter...}

House-bound, bored, bored, bored, I've recently downloaded a lot of budget files, including some massive DAZ freebie packs, as yet still zipped. I never thought I'd say this, but my E: Drive is down to 200 GB free. I fitted a SATA slide-mount drawer when I built this CAD-Tower, am about to load it with a WD 'Black' 4TB for my Poser & CAD stuff...

Sorry, yet another rant about FBX import. Yes, when the FBX is correctly rigged, with a complete hierarchy, it works like it says on the tin.

Of course, to reach that stage, you may have to do a 'binary chop' to find a usable import scaling. Default is 100%, but I've had them range from ~0.5% to ~3500%, with several I never did find... Please, like OBJ import, may we have a 'scale to figure' option ??

Then you discover eg the body is welded as a solid mannequin. Posing requires heroic surgery & re-rigging, both currently beyond my wits.

Worse, body, clothes and accessories may import as a flock of components in loose formation. Really requires re-rigging, but 'Plan_B' is to use hierarchy display to mass-parent them to a low-poly place-holder such as Les Bentley's free 'MinFig' or Anthony Appleyard's free 'Dummy',

(Latter may need origin re-setting, then saving to library as eg 'Dummy000' prior to parenting. Such re-setting was trivial in P4, but P11 makes it hard. With nothing apparent in P11 PDF manual search or index...)

Thus parented, you can easily pivot FBX from typical horizontal posture, scale the last +/- 25 % from your best-guess, 'At Least It Is On-Screen' import scaling. Now, you notice several parts are missing. A further search finds eg face and hair went astray at import. Gotta back-track. In fact, usually easiest to delete and re-import, now with a better-guess scaling....

Then, how do you persuade your imported FBX to use an associated texture directory ? When you open FBX in eg Windows' 3D Paint, it may prompt for such. P11 either gets it mostly-right automatically, or totally muddles the materials. No obvious way to 'browse' to the set, and a real pain to manually import umpteen textures via material room. Which usually requires me to have free Autodesk Toolkit's 'FBX Explorer' open, too, as there's no obvious equivalent of an OBJ's MTL look-up list...