Great looking set of fixes.

I see you cleverly saved some fixes for 6.03, too.  Job security, eh?  ;)

Looking forward to doing the update this evening.  :)

Not essential but worth doing when you have time to ensure your embedded content is up to date.

It's all there on my system:

Since only a few items have been updated, it would help if we just had to download a "mini" pack containing only the new assets. :):cool:

As I recall you have both iClone 6 Pro and iClone 6 Standard. Is the Plugin tab missing from Pro or are you looking in the Standard version for this? Like others the Plugin is available in the Pro version for me.

BTW, downloading seems up-to-speed again.

I can confirm. Even though Horizontal Flare is now horizontal, the Vertical Flare is still missing as was reported before. For example, this is what the Spectral Cross looks like (which combines Horizontal and Vertical Flare):

This was reported quite some time ago, so it would be great of this got fixed before 6.0.3, as this is hard to work around.

Specs: i7 2600K; GTX 980; 16 GB RAM; Windows 7 Pro SP1.

These are still two problems I reported that are related to shadows.

One is that the shadows for spotlights don't work correctly as discussed here: https://forum.reallusion.com/FindPost220528.aspx.

The second problem is shadow duplication in larges scenes as reported here: https://forum.reallusion.com/FindPost220709.aspx.

I discovered that in a large scene of a city in the desert there was a shadow without anything that cast a shadow nearby. In a test project I was then able to replicate that clearly.

I don't expect Reallusion to list everything.  I'm sure they know of issues we haven't reported here.  I don't know any software company that does that.

But they say they're tracking all our reports, especially ones posted in the "Official Issues" threads.

Sure, an ambitious person could scroll through all 28 pages of the 6.01 entries, and all 73 pages of the 6.0 entries, weed out conversational (not bug report) ones, weed out the duplicates, and compile a list of all reported issues, then subtract the fixes from 6.01 and 6.02....... or Reallusion who is already tracking them could do that for us.

That would save us the trouble of trying to remember what's already been reported.  There should be no need to waste our time writing up reports on known things, or reading through 100 pages of entries (search is hit-and-miss if you don't search for the magical same phrase as what was used before).  And there should be no value in burdening Reallusion with duplicate reports, right?

Just a thought.

It would be good to know what is recognized as a bug, what has been resolved, what is still being worked on, etc. Then we'll also know what has been overlooked.

And perhaps give bugs an identifier and a description.

EDIT: It would also be helpful for us to get more feedback from RL, such as we got from Soya for a while.

But, similar to the "fixed" list, a simple list of unresolved items posted in this forum (already public knowledge) sure would be a nice step.  It would also make it possible for us to know if they have overlooked something.

Example:  There were two "glare" issues.  One was fixed, the other not.  Is the un-fixed one on the ToDo list, or was it overlooked?

Does this also happen for the non-trial (purchased) version?

Now that's more like it.  :)

I'm glad the "uninstall/reinstall the plug-in" will not be a normal part of the update process.

Thanks.

As reported in this post, the convert position to path outlined in the help file still does not work.

The description of this fix is not quite clear to me, but sometimes Cameras are still showing when they are selected as hidden.

According to the iClone 6 Help, you can delete the corner pins and then simulate a cloth that is held in the center, while the corners fall down. However, this is not what happens. After removing the corner pins, the cloth still behaves as pinned at the corners.

I was able to repeat this, following the instructions in the Help.

EDIT: As was pointed out by rampa, this does work with Bullet physics, but since the physics type cannot be set per object that is not really a viable solution. The iClone 6 Help mentions the pinned cloth as one type of Soft Cloth but does not state that it only work for Bullet physics.

Soya, I'll try to see if there is a specific condition that causes this to happen. Others have observed this behavior too, so it's not just me.

Already requested by yours truly (Justaviking)... https://forum.reallusion.com/Topic190631-298-1.aspx

And then again a few months later by JC Weatherby... https://forum.reallusion.com/Topic199950-298-1.aspx

I know some of you are concerned that the issues are not being recorded, but I can assure you that everything reported in this thread is seen by the development team and logged.

If you have posted issues anywhere else on the forum, I would urge you to also include them here (or a link back to your original post). This will ensure nothing gets missed.

It's probably random, because until now I have not been able to reproduce it again. It was a fairly large project where it occurred. So if anyone else discovers a pattern, please post.

What it amounts to is that only half of the timeline gets rendered (even with all frames selected). So if you have a total of 10 seconds, only the first 5 a rendered.

When I tested this, I rendered to MP4, and found that the length of the clip is as expected, but the second half is just a frozen frame.

However, when I repeated the test with image sequences, it turned out that all frames were rendered. So it seems to occur only when rendering to a video file.

EDIT: This same issue has now also been reported by the originator: https://forum.reallusion.com/FindPost225708.aspx.

I noticed the same, so it's not your system. I agree, the IC5 way was better.

That, my friend, is a favorite newbie question.

While editing, iClone displays 60fps on the timeline, which is its internal heartbeat.  So one second is 60 frames according to iClone.

However, when exporting, it exports at 30fps.

You still get 1 second of footage, but only 30 frames.

So the TIME is the same, but the FRAME COUNT is half.

I'm not supporting iClone's behavior.  I was merely trying to explain it.

I have worked quite a bit with NLE software, testing a variety of video sources, including both NTSC and PAL.  I remember a huge fuss when the software ran a 30fps rather than 29.97fps.  Even that 1% difference was a big deal, because either see a stutter in your film every 100 seconds you'd or your sync would drift off.

This is one of those thing (to me) where I don't really care how it is done under the covers, but as a user I'd like to "see" a specific frame rate when I work; either "30" fps or 60 fps, or even 24fps if I want to mimic film rates.  And I should be able to change my mind in how I *display* it on the timeline if I want to.  And I should be able to render to any of those framerates, regardless of what I used while editing.

I've posted passionately about this multiple times.  It's not a show-stopper for me.  But it should be better.  It's one of those things and almost *every* user encounters, usually resulting in confusion and even frustration.

Not to be picky, but that's only a 0.1% difference. A 1% difference would be quite problematic indeed.

It's really unfortunate that we still have to deal with archaic frame rates like 29.97 from the old NTSC days.

I shall self-administer 30 lashes with my slide rule.

(No, I don't actually own a slide rule.  But I did learn how to multiply and divide on one once, as a novelty.)

It wasn't until several months ago that I bothered to learn WHY it is such an odd value.  Our electricity here is 60Hz, so why not use a simple "half" value of 30fps?  In essence, it had to do with compatibility between B&W and Color systems.  From Wikipedia, the knower-of-all:

The NTSC field refresh frequency in the black-and-white system originally exactly matched the nominal 60 Hz frequency of alternating current power used in the United States. Matching the field refresh rate to the power source avoided intermodulation (also called beating), which produces rolling bars on the screen. When color was added to the system, the refresh frequency was shifted slightly downward to 59.94 Hz to eliminate stationary dot patterns in the difference frequency between the sound and color carriers, as explained below in "Color encoding". Synchronization of the refresh rate to the power incidentally helped kinescope cameras record early live television broadcasts, as it was very simple to synchronize a film camera to capture one frame of video on each film frame by using the alternating current frequency to set the speed of the synchronous AC motor-drive camera. By the time the frame rate changed to 29.97 Hz for color, it was nearly as easy to trigger the camera shutter from the video signal itself.

Sometimes this is the down-side of being on the cutting edge of technology.  Then later another country (or company) starts fresh using the lessons-learned, but makes it less of a Frankenstein system.

The earliest you can go is 1/1/2008. Adjust the period and then click Search.

These have all been passed to the iClone team who are now hard at work on the next big update which is 6.1. This is currently scheduled for release in April. Please do continue to report any other issues you may find in the meantime.

lpatter specifically mentioned the MarketPlace for which I gave a solution.

This problem has occurred in the past with some previous version of iClone, but I don't remember if there was a solution for it.

Please make the "Installer" more robust

Actually, many of us would prefer to see it go away, and just give us executable installation packets that we can download.

Recently trying to install the "Substance 200" pack, I ran into a missing DLL problem.  The installer should handle problems like this more gracefully.

Many

• Reported in this post:  https://forum.reallusion.com/FindPost229235.aspx
• Final resolution posted here:  https://forum.reallusion.com/FindPost229457.aspx
• See Animagic's excellent post, immediately following mine.

Many installation utilities will offer to help install the missing items for you.  Example:

• "This installation requires Microsoft C++ library blah blah blah, would you like to install it now?"

Something like that.

ADDED... March 23rd...

It's not just me.

https://forum.reallusion.com/Topic230273-13-1.aspx

Here's a picture...

Note that the recommendation is a bit vague.  Which program is "the program"?  iClone?  Substance?  Java?  .Net?

This situation should be preventable, or at least made much easier for the user.

.

Some would consider it an honour. ;)

Sounds like iClone is going old school on you there. ;)

Could you let us have your project so we can check this out. Thanks.

It's a large file, almost 350M zipped. I'll PM you a link to it. 

EDIT: Link successfully posted. This project has also developed another problem, which is that a sound file I added no longer plays. That's old school too...:unsure:

Thanks for the link. I will let you know as soon as I get some feedback from the iClone team. :)

Anyway, my problem is that I have a project with multiple dialog tracks, but some of them are muted on preview. The lip-synching is working and the rendered output has all the speech in it. If I start deleting tracks that I can currently hear, then others become audible. It is as if there is a maximum number of tracks.

Peter or Soya: you will find this issue in the file I sent the link of yesterday.

As you can see, the timestamp of the file TW_S01_3e.iProject in the Content Manager is different from the timestamp in Windows Explorer. I had just saved the file by overwriting, but the timestamp is not updated.

This is confusing, especially if you keep multiple versions of a project and want to know what the newest is. It doesn't help to leave the folder in the Content Manager and then return to it; the timestamp doesn't get updated.

I had a similar problem with static noise. I had a scene with dialog and a WVM video on a projection screen (plane). The dialog was fine but the sound of the video was all static. So something is wrong with the sound.

I have a project where a couple of characters walk along a path. The path is set to be projected to the terrain. However, when I open the project again, I always see the following:

To correct this, I have to uncheck and recheck the "Project to Terrain" setting for the path. After that, things are fine.

However, I have discovered a problem when the character speaks: the teeth don't show correctly (they seem almost hidden). The regular standard G5 characters don't have that issue.

I discovered a workaround: when the Facial Features dialog is open while the character speaks, the teeth show, although still not quite correctly. The tongue animation seems to be gone as well.

The following clip shows the problem and the effect of the workaround. The character on the left, Gwynn, serves as reference. The character on the right received a new face in IC6 and has the problem.

Hopefully this can be fixed for 6.1...:P

When you try to save a project under a new name or try to save a new project, the default name "Project" that is provided is not globally updated when you change it in the Content Manager.

The name in the Content Manager is changed, but the name in the iClone title bar is still "Project". Also, if you do a save, it saves it to a file named "Project", which will then appear in the Content Manager, not to the new file name. Only if you select the new file name and overwrite it with your project will the file name be permanently updated and show correctly in the title bar.

What concerns me is that these are fairly basic problems that should have been caught in testing. I don't mind reporting them, but who knows what I've missed...:unsure:

I can confirm that problem. In my case it was two times; still one too many. There doesn't seem to be a clear cause; it just happens.

The next update 6.03 will correct a number of the issues mentioned. It will also add support for the Mocap Device Plugin and Kinect v1 devices. This is due later this month.

The larger 6.1 update will now come towards the end of the 2nd quarter and add a number of improvements including support for Kinect v2 devices such as Kinect For Xbox One (with adapter) and also add the long awaited additional functionality for the G6 characters.

Please keep your feedback coming. :)

Just to let you know this issue is fixed in iClone 6.03. :)

Fixed in the upcoming 6.03 update. :)

This has also been fixed in the iClone 6.03 update. :)

Should now work correctly with the iClone 6.03 update. :)

Fixed in iClone 6.03. :)

Also fixed in iClone 6.03. :Whistling:

Should be working correctly after the iClone 6.03 update. :)

When you start the "Official 6.03 Issues Thread," please list both the fixes (as done before) AND the KNOWN REPORTED ISSUES that will still exist in 6.03.

That will save us the trouble of re-testing, re-banging our heads into, and re-reporting things you already know about.

Looking forward to the release!  :)

We've had a little delay on this but it is now due around the last week of April. :)

Unfortunately the "Glare" issue should now be fixed in the 6.1 update which is scheduled towards the end of the second quarter. For the G6 characters we are currently looking at adding support for them in 3DXchange 6 at the end of the 2nd quarter, with additional tools coming in the 3rd quarter.

Unfortunately not in 6.03. Should be fixed in the next update which is 6.1.

Well as it is planned to be fixed in 6.1 I'm guessing the cause of the problem is known. ;)

Unfortunately the plans are not finalized so I can't really reveal anything specific yet. Generally speaking the G6 characters will remain one piece like Daz characters, but we will add additional tools to allow customizing these characters and add custom faces. In addition there will be G6 CloneCloth for creating custom clothing.

What is the "mega problem" you mention? Daz characters work fine in iClone 6 as long as you have a system that meets the recommended specifications. Sure you can't put a dozens of them in your scenes but one or two should play nice. Please can you elaborate on this "mega problem" a bit more. Thanks.

Can you explain what you mean about the "2nd facials". I have no clue what this means. :ermm:

Again you mention mega problems, errors in every part, but don't really explain what the problems are. I guess we are both using the same software but I don't see all these mega problems that you are experiencing. You will need to explain in more detail so we can try and help you. Making bold claims without backing it up with detail doesn't help anyone.

All our efforts are dedicated to improving iClone 6 at the moment. There is zero chance of us going backwards to start making additional plugins for iClone 5.

I looked at your screen capture and I think your problem is that the texture is linked (it is an external texture).

This is an option when exporting from 3DXchange. Make sure that "Embed External Textures" is selected. This will make the textures part of the file you export. You should now be able to edit your weight map.

I can tell you're upset, and I can see why.  I thank you for taking the time to provide a mature and useful response.  It was a good summary.  (I'm *not* being sarcastic; I'm being sincere.)

I, too, wish things would get fixed faster.  There is a reason we were using iClone 5.5, rather than 5.0 or even 5.3.  It is difficult to be patient (I really thought 6.1 would be out by now), but I trust we'll see iC6 continue to improve.  Until then, we hold their feet to the fire and do our little part to help define priorities.

Imagine were we might be by the time we see 6.3 or 6.4!

For now you can click the ʺCurrent Frameʺ button on the Timeline. That will move the timeline to the current frame. However we will try to improve this feature in a future update.

This has been a long-standing problem already present in iClone 5.

I like your idea of adjusting/turning off the effect by direction.