Lets say that historically this kind of random (per user) behaviour (errors?!) just happen with those that are using Intel video card. Just check the old forum and you will verify this.
I can use the latest version without this problem in a PC with the recent Intel HD onboard "video cards". But, I have other - some times some edges disappear. (did you have experienced this one?)
But, I don't have any problem when using in a machine with AMD Radeon or NVidia.
I use to verify all errors reported in order to not charge the Wings3D' main devs with minor things. If I can't reproduce it using the same brand that's a problem - there is no way to investigate.
Try to record the steps sequence and maybe - following the exact same steps - we can try to reproduce it.
As a programmer, you know that we can just try to fix something only if we are able to reproduce the error. And, if the problem is driver/hardware related, we will be able to verify the issue only using the same configuration.
So, I don't think this is a shame - I can't have so many hardware, OS or anything else we can find all around the word - I have limitations.
[edit]
maybe we can compare the gpu extensions caps and try to find something to verify. I attached my infos.
It would be good if you could use GPU Caps Viewer 1.19.0 to extract your information (in the Tool tab you will find the export option) - look for the download button (down on the page).
I can use the latest version without this problem in a PC with the recent Intel HD onboard "video cards". But, I have other - some times some edges disappear. (did you have experienced this one?)
But, I don't have any problem when using in a machine with AMD Radeon or NVidia.
(11-14-2013, 05:19 AM)JonnyMac Wrote: I'm not interested in debating you on this pointBut, after you said "I think it's a shame that this happened" you should.
I use to verify all errors reported in order to not charge the Wings3D' main devs with minor things. If I can't reproduce it using the same brand that's a problem - there is no way to investigate.
Try to record the steps sequence and maybe - following the exact same steps - we can try to reproduce it.
As a programmer, you know that we can just try to fix something only if we are able to reproduce the error. And, if the problem is driver/hardware related, we will be able to verify the issue only using the same configuration.
So, I don't think this is a shame - I can't have so many hardware, OS or anything else we can find all around the word - I have limitations.
[edit]
maybe we can compare the gpu extensions caps and try to find something to verify. I attached my infos.
It would be good if you could use GPU Caps Viewer 1.19.0 to extract your information (in the Tool tab you will find the export option) - look for the download button (down on the page).