There've been about a billion variations on the old crook-neck lights made over the years... small wonder though, they've only been in use for something like 70 years in various forms. Heck, they even sell knock-off types for camping at sporting goods stores. Hell of a long service life for a product that started in WW2... :)

No worries... I really do appreciate this and thank-you!

I haven't run in to too many issues exporting raw obj's from DS... but I do know that weight maps won't transfer properly to Poser cr2, and that any specially purpose-built shaders won't either (I used Iray as an example before). I do know that certain other things don't play well between the two programs (I'd written a tutorial on using Poser items in DS a while back that covered most of what doesn't transfer between the two programs).

The DS fbx import/export has been wonky for ages, sometimes it works and sometimes it doesn't... 3ds import doesn't always work either. I've become very proficient at knowing how to work with DS to make things directly compatible with both programs without needing DSON or special scripts... :)

Yes you can export obj files from DAZ Studio, if the export settings are used properly most textures should be ok, but of course custom materials or IRay settings won't transfer well (or at all)... among a few others. You can also export Poser Cr2's from DS for use in Poser, though the weight maps won't work, and there may be other issues such as morph functionality problems (depending on how the morphs were made in the original figure)...

I also know that the DS figure and rigging tools can be used to create Poser content directly, including Poser-compatible ERC coding and Morphs... I use it to set-up and rig all my figures as Poser-ready content (I had a hard time using Poser's figure set-up room and tools and found DS easier to use, as that's what I started with before learning Poser). Now days I use both DS and Poser as integral parts of my production pipeline...

Thanks I appreciate it and I'm sure the other history buff's in our community would too! :)

This was the WW2 version in case you wanna take a stab at it as well... They were fairly close to the same size but the WW2 was all metal and only had a single replaceable glass lens, instead of the plastic lens/filter lens combination...

Technically, WW2 Web-gear should include a variation of this as well... an all metal crookneck flashlight was GI issue for WW2 Para's and Rangers (though a slightly different shape originally), they were also adopted by British forces, and the 60's era version replaced the earlier model for wide-spread use in most NATO countries...

I should mention that the outer casing as well as the lenses are plastic but the switch, thumb button, switch housing, and belt clip are metal and riveted to the plastic casing in case that is important for materials set-up... and the two lenses in the head are spaced about an inch apart, each with its own removable housing to replace lenses and give access to the bulb and reflector. The base unscrews to change the batteries and to access the spare bulb and replacement lenses, I know it's not really necessary in a prop item, but I wanted to include the info just in case...

It's roughly 8 inches tall with a body of roughly 2 inches wide and with a lens 3 inches wide (including the lens housing). It takes 2 D-cell batteries, and the base has a compartment to store the spare lenses and a replacement bulb. There are two lenses inside the top covering a single incandescent bulb, the inner lens is clear plastic, and the outer lens is replace-able (the lens housing can be taken off) with either a clear lens, red filter lens (usually used) or a semi-opaque white lens. The switch on the side has 3 settings: Off, Signal, and On, and when in the Signal position there is a thumb button just above the switch that can be pressed to toggle the light on and off to send Morse code signals. There's a spring-steel clip on the back to allow the light to be attached to a belt or clipped to web-gear...

I dug out my service issue one from my field kit to get the measurements... they've been standard kit issue since the 60's but no set of GI gear I've found includes it and they should... :)

I'm all for learning new skills, and am constantly refining those skills I do have, but having to re-learn the interface every time a program update is released takes time away from skills development and it shouldn't...

I can certainly understand the need and desire of companies to add new features and functions to programs... and the desire as a user to want updated features. What I don't understand is why it seems necessary to unduly complicate the user interface to add the new features at the expense oft-times of user friendliness. I'll also never understand the ever-expanding need for higher and higher system resources when no truly new features are added. It seems in many cases that the system requirements and UI complexity are made needlessly bloated for no real noticeable gain or function, and features that were once easy to find often get buried in ways that make no common sense what so ever. I also have a hard time understanding the need to "force" users to spend 100's or 1000's of dollars to keep hardware up to date with the constant program updates that expand system requirements without adding any truly new features. Lastly, I'll never understand entirely the constant need of software developers to insist on "fixing" good software by adding "improvements" that frequently break parts of any program that were working perfectly fine in previous versions. Improvements shouldn't come at the price of user friendliness and broken features that used to work just fine.

There's an old adage "If it ain't broke, don't fix it..."

I don't mind upgrading programs if it will add some truly new features, but being forced to spend money on upgrades to hardware and software simply because someone somewhere decided I should have to for the good of their pocket book gets to be a bit much at times. I find that much of the time that software becomes "bloat-ware" for no good reason except to force users to spend money on system upgrades and hardware simply to try and keep up with bloated system requirements where they weren't necessary... I have to assume that most software developers get some really nice kick-backs from system component companies in exchange for instilling the need to constantly upgrade hardware as a base part of the development process, unfortunately not everyone can afford to constantly upgrade their systems every time they need to update a program...

I use UV Mapper Pro constantly and also sometimes classic (on smaller projects)... it remains an incredibly useful part of my modelling tool box and works just fine in Win7...

Good to see you around again! :)

Swimming Poses for Kristin and Hiro 3 now available free!

Features 10 swimming action poses each for Kristin and Hiro 3. Poses include; Back Stroke, Breast Stroke, Cannonball, the Crawl, Low Dive, High Dive, Treading Water, and 3 Underwater Swimming poses. Can be used for all your beach or pool scenes, and works perfectly for the free SCUBA set for Kristin in the Wardrobe!

Find them here... http://www.schells.ca/the-catwalk!

And don't forget the free SCUBA Diver set for Kristin found here... http://www.schells.ca/the-wardrobe!

Looks like a good build so far... nice work... :)

Thanks Digitell... It's pretty awesome! :)