Full Version: V4 beta Nov-13-2017 available now

Show messages:  1-12  …  33-52  53-72  73-92  93-112  113-132  133-152  153-172  …  213-231

Hi Michael,

only detail... changing of Style of grid and accented grid lines doesn't work. Color and Width work normally.

I'm not sure if it's problem only on my computer or it is the general problem.

Mik

---

Hi Pilou,

re:
> Does exist a trick for reccord artificially like a "rapport error" ?

Well if you have a crash a crash report dialog should show up, but it sounds like you're running into something a little different than a crash. I'll take a look at your file.

- Michael

---

Hi Metin,
I've the same configuration and

ImportObj, Subdiv-beta9 work

BlendCap and Nudge scripts work also

only
Heightmap
sBridge
sScale
sSplit

don't work for me.

---

Thanks Michael.

@You "...I just need to know what isn't working the same..."

Ok. Got it!
ASAP I will let you know.

---

Pilou really I don't understand why you can't make a video :)

I use MonoSnap for example.

Run Monospnap and record the whole desktop or a portion of it. It doesn't matter what crashes or not.
Monosnap records everything is displayed by the computer's monitor.

Ciao!

Marco (mkdm)

---

What is the interest of a video that show a frozeen screen ? :)

Here with V3 the SetDir not kept

---

Hmm… Come to think of it, the failing commands could be due to deleting V3, as the commands were part of the internal folder structure of V3. Didn't think of that because the shortcuts had remained intact.

I'll check this a.s.a.p.

Regards,

Metin

---

Hi daniii, thanks for testing it on Linux with Wine!

So it sounds like it's pretty close - with snapping not working does it start working ok if you turn on View > Display hidden lines or still the same? With Display hidden lines turned on snap point visibility doesn't need to be calculated which is done by texture readback from the graphics card back to the CPU side.

For selection not working that's also either a texture readback problem or it could possibly be antialiasing being forced on, it's not good for selection related data from a draw to get mutated by antialiasing. So if you know of any controls for force enabling antialiasing try turning those off.


> You mentioned a while ago that it can work with OpenGl or DirectX. Is there an OpenGl mode?
> As far as I can tell it still uses DirectX.

Yes the Windows build can use either Direct3D11 or OpenGL. The way it's supposed to work is if it sees that it's running under Wine it uses OpenGL (with the theory being it's a much thinner layer around OpenGL provided by the OS) otherwise Direct3D11. Maybe the Wine detection method isn't working with Wine64 anymore, one way to tell that is do you see native UNIX path names shown where file paths are displayed like in the recent files list?

I can introduce a flag to allow you to force either Direct3D11 or OpenGL mode, maybe the other one will work better.

- Michael

---

Hi Pilou,

> No need video : all functions are freezed : impossible to click on button Cancel etc...
> So some ennoyous! :)

Does it only happen when you're dragging a particular thing? Maybe it's related to history recalculation if you have a long chain of things to update. What happens if you select all your objects and turn off history updating by using Edit > History > "Disable update" button, any freezing after that or not?

- Michael

---

Pilou....evidently I didn't make that clear :)

I don't want to see a "frozen" screen but I want to see a video showing what you did until Moi's got frozen.
All the steps you did....

I hope this time I made myself clear :)

Ciao!

---

I just draw a box or a plane , make some extrude edges as the video above
http://moi3d.com/forum/index.php?webtag=MOI&msg=8675.98
goto to forum
return to Moi
= freezing all modeling functions!

If i stay inside Moi no problem!

So for me suspicion of Multi task problem! :)

---

Nearly all commands I mentioned (ImportObj, Subdiv, SubdivClassic, Nudge and BlendCap) do work, my apologies, I didn't think of the commands being a part of the integrated application folder structure on the Mac, while MoI.ini is stored externally. Now that I've copied the commands to the Commands folder of MoI V4, they work, with the exception of FatLines.

Maybe it'd be more clear if non-present commands would give a "Command not found" message, in stead of an "error in line 1", because that suggests an error in the command in stead of the command not being there.

Regards,

Metin

---

Hi Metin, thanks for the feedback!

> • Some keyboard shortcuts I had assigned to Command + key have been automatically
> changed to Alt + key, such as Alt + I for ImportObj in my case. But pressing Alt + I didn't
> work. Then I reassigned it to Command + I again, and the shortcut worked. Other Alt + key
> combinations such as Alt + O to open a file do work though.

Yeah I think this is an accidental side effect from how the Wineskin version internally used the Alt key as an alias for Cmd, I'll have to think of what to do about this. To maintain compatibility with V3 I may have to disallow using Alt shortcuts in V4 since V3 can't set Alt shortcuts. I'm not sure about this yet.


> • Pressing the Mac OS system shortcut to toggle full screen mode (Control + Command + F) doesn't work.

Yeah I think several key shortcuts for things like switch between windows are probably missing too, I'll have to make a pass through these.


re: Loft problem - that break apart thing sounds likely related to using "Exact" mode on the Loft, Exact NURBS circles and ellipses tend to behave like that, they are made up of 4 arcs with "corner points" on them. I try to hide this normally by replacing something like a circle or a sphere with a squishy non segmented version if you edit control points. I think it's likely to be the same behavior as V3 but if you can post the 3DM file I can take a look and see for sure.


> • The viewport labels (Front, Perspective, etc.) initially show as blocks:

That's odd but those are just temporary they'll be replaced once I get text drawing in the viewport working.

Thanks! - Michael

---

Ok. Got it!

Tested and...no! No problem for me at all. All worked fine.
No problem of "Multitasking" or other kinds of issues.

Ciao.

---

Hi Dinos, thanks for testing it!

> The only thing that i noticed is that the scripts that use moi.ui.createDialog will not return focus to
> the main Moi window after i close the Dialog if Moi is running full screen.

Yeah I think I've seen this also happen after the file dialog is used as well when placing a background image, it's on my bug list.

The moi.ui.createDialog one might be related to MoI doing some stuff to keep the dialogs above the main window, I had to fight with things for a while to make that happen , macOS seems to want to allow dialogs to go underneath a "main window" by default.

- Michael

---

Hi Mik,

> only detail... changing of Style of grid and accented grid lines doesn't work. Color and Width work normally.
>
> I'm not sure if it's problem only on my computer or it is the general problem.

Dashed and dotted line styles are not implemented quite yet so no matter what you set them to you'll only get solid lines for right now. They will be coming back though.

- Michael

---

Hi Michael,

You're very welcome. Thank you for making the V4 beta publicly available.

I'd welcome having Alt as a keyboard shortcut option, because a lot of commands share the same first letter (Rotate, Revolve, RailRevolve, etc.), but it's not important.

Regarding the Loft issue: you might be right. I'll do some more tests.

The blocks in stead of viewport labels might be due to my slightly dated NVidia card. I've got the last iMac model that had an NVidia graphics card, before Apple completely switched to AMD graphics cards.

As an extra bit of information: I'm using the latest NVidia Web drivers for my NVidia GeForce GTX 780M.

Good luck with everything!

---

Hi Metin,

> Maybe it'd be more clear if non-present commands would give a "Command not found" message,
> in stead of an "error in line 1", because that suggests an error in the command in stead of the
> command not being there.

The tricky part about this is that in addition to command names you can also put script code directly in a keyboard shortcut. When you get "error in line 1", it's because when it saw that the text in there didn't match an available command name it tries to execute it as literal script code to try and get it to do something.

- Michael

---

Hi Metin,

> I'd welcome having Alt as a keyboard shortcut option, because a lot of commands share the
> same first letter (Rotate, Revolve, RailRevolve, etc.), but it's not important.

It could be possible that it's an option that you can enable if you don't need to keep things compatible with V3.

But the thing I'm not sure about is if they can be enabled and also maintain compatibility with V3 at the same time.

- Michael

---

Metin
>> Max's FatLines script returns an error
I'll check all my scripts today evening

Finema
I fixed sBridge, sScale and sSplit scripts yesterday. Not published yet.

to all:
Dear friends, if you noticed any compatibility problems with my scripts, please post your bugreports to this thread:
http://moi3d.com/forum/messages.php?webtag=MOI&msg=6837.1

---

Show messages:  1-12  …  33-52  53-72  73-92  93-112  113-132  133-152  153-172  …  213-231