G9 to G8.1 Conversion

Home Page Forums General Chat G9 to G8.1 Conversion

Viewing 7 posts - 31 through 37 (of 37 total)
  • Author
    Posts
  • #2055301
    eelgoo
    Moderator
    Rank: Rank 7

    The trouble with that is that you need to have the G9 bloat installed.

    It would be more efficient to be able just to define the morph source duf & work from that onto the G8 / 8.1F base.

    :0/

    #2055354
    Spats
    Participant
    Rank: Rank 4

    @necro, @eelgoo, et al

    Speaking of the "original" conversion method (linked from WP Guru/Verslice). Who here has had success with it?

    Have, since, upgraded SSD and broken down and installed G9 bloat for other reasons (I know I know, "never"). But with running older (pre 4.21) DS, cannot get G9 Dev Tools v0.3 scripts to run. (Yes, tried running individually from files, but each in tutorial still errors out.) Verslice mentions what the core of each script does in background (@1:25, "Set G9 to Shape" = set a new base shape; @4:55 "Create Follower" = transfer utility). But when attempting each manually things still don't work, so something seems different. As well the final step (@6:08 "Update Follower Base Shape") has no equivalent background action mentioned to manually try prior to the final "Set G9 to Shape" script run (set new base shape to reset). So not sure what to do without working scripts or a manual workaround (besides upgrade DS or run parallel to test).

    Just wondering who's been successful with the WP method, and under what conditions.

    #2055427
    DirkDiggler
    Participant
    Rank: Rank-1

    I use 4.16 on primary machine. I have a secondary machine (Laptop) that I have 4.21 installed to do those little things. There is no GPU installed. I don't render on it. I just use it to do those little things like add Volumetric fog in a scene. Or the Dev tools.

    #2055481
    Spats
    Participant
    Rank: Rank 4

    @necro Ok, so seems 4.21 may be the prerequisite for G9 Dev Tools or its respective scripts to function properly - or at all. I've considered installing most recent and updated on a separate older machine for similar purposes, as well as the thought of running parallel on primary machine with separate, renamed folder technique outlined here at Zone. Latter has worked well for running a slightly more recent DS ver for the same things you use it for (volumetrics and other tools), (though apparently it's still not recent enough for G9 Dev Tools/scripts to work); but always leery about installing and running another version in parallel and screwing things up with runtime references or other.
    Going to have to backup and get brave eventually I suppose.

    #2055490
    eelgoo
    Moderator
    Rank: Rank 7

    Well I have run the main public version & a recent Beta off the same remote Library installation for years.

    Never had an issue with doing that.

    🙂

    #2055553
    DirkDiggler
    Participant
    Rank: Rank-1

    @eelgoo Same here. Different version pointing to my library. Everything still works either version. The only issue I had was with two installs on the same machine. I found dForce hair would randomly use a different version Ie If you run dForce on something in 4.21 it will not come out the same as you did in 4.16. And having both versions on the same machine seemed to lead to random.
    So if you rendered the scene. Then cleared and reloaded the same scene. The dForce would be different. Too me every to figure out it was the two versions. So beware that.

    DD

    #2055580
    eelgoo
    Moderator
    Rank: Rank 7

    Ah, I see.

    I never use dforce, so I wouldn't have been aware of that.

    🙂

Viewing 7 posts - 31 through 37 (of 37 total)
  • You must be logged in to reply to this topic.

 

Post You Might Like