Hi Marco,

re:
> Please, keep in mind to allow as to resize the first column on the editor.

Please try the updated shortcut key editor from here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=8682.52

With that update, the first column should automatically expand to fit the widest shortcut key and so none will be cropped and there's no benefit to gain from also adding in column resizing.

- Michael

Hi Metin,

re:
> • If I enter a Command key shortcut, such as Cmd + E for export, then the next time I start
> MoI, the keyboard shortcut has changed to Alt + E, and neither Alt + E nor Command + E
> works.

This has to do with Wineskin using Alt as an alias for Cmd since Windows doesn't have a Cmd key. In MoI v3 you could use either Alt or Cmd for any of the Cmd shortcuts, they couldn't be set separately. I haven't quite figured out what to do about this yet.


> • When the Obj export dialog is active, you can't navigate a viewport without exiting
> the export process. I use viewport navigation a lot when the export dialog is active, to
> zoom in on objects and check if the polygon detail is sufficient everywhere.

I can't seem to reproduce this one over here, is there a particular method of view navigation that's not working? What happens when you click on the main window while the meshing options dialog is open, does it make a sound? By the way the weird little Mac classic wristwatch cursor will be gone for the next beta.

- Michael

Thanks Michael for the updated "ShortcutKeysOptions.htm".

It works.

But...we have another problem here, and this is more serious :)

As I told you in my previous message I remapped the "Ctrl+Shit+1" to "Ctrl+Shit+!" and all works fine until I only use V4.

But, when I close V4 and open V3, where I still have the "Ctrl+Shit+1" original shortcut, and then I reopen V4
the shortcut key is changed from the new "Ctrl+Shit+!" to the original "Ctrl+Shit+1".

But...V4 and V3 does share the same .ini file ? I hope not.

So, to recap, this is the step I did, if you want to make a test by yourself :

1) All Moi are closed
2) I open V4
3) I remap the "Ctrl+Shit+1" to "Ctrl+Shit+!"
4) I close V4
5) I reopen V4. All is as excepted. The new shortcut is there and it works.
6) I close V4
7) ************* I open V3 and check the shortcut keys : I have the original "Ctrl+Shit+1". OK, this is correct and it works.
8) I close V3 and open V4 again.
9) ************* Here's the issue. V4 lost the new shortcut "Ctrl+Shit+!" and instead have the V3 shortcut "Ctrl+Shit+1"
10) If I repeat the whole process I always get this issue.

I remember you that I'm running Windows 10 Pro 64Bit Eng.

Please check this issue when you can.

Thanks.

Hi Marco,

> But...V4 and V3 does share the same .ini file ? I hope not.

Yes they do, same as V1 and V2 shared the same .ini file, same with V2 and V3, and so same with V3 and V4.

But yes this is a problem that the shortcut keys for certain cases are interpreted differently. I'll either need to make those cases compatible or otherwise use a separate section in the file to save V4 shortcuts so V3 and V4 would be independent from one another in that particular area. Making them exactly compatible may be tricky to do in a cross platform way since it relied on some Windows functions.

- Michael

@You : "...Yes they do, same as V1 and V2 shared the same .ini file, same with V2 and V3, and so same with V3 and V4..."

Ok. I didn't know. Thanks for the info.

But the issue remains...

@You : "...otherwise use a separate section in the file to save V4 shortcuts so V3 and V4 would be independent from one another in that particular area. "

I think this could be a very easy way to solve this issue.

Thanks.

Hi Michael,

My viewport navigation controls are:

• RMB = rotate Perspective viewport or pan orthographic viewport
• Control + RMB = zoom
• Shift + RMB = pan Perspective viewport

If I use either of those controls outside of the export dialog, the export dialog exits. Maybe the RMB cancels the export operation?

A positive note for now: I couldn't manage to recreate the selection drag lag. It might have been caused by MacOS having been active all day without restarting, causing fragmented (video) RAM and such fuzzy causes. I'll let you know if I encounter it again.

Hi Metin,

> If I use either of those controls outside of the export dialog, the export dialog exits.
> Maybe the RMB cancels the export operation?

Yeah right now if you do a right click in a viewport it will cancel the export. That's kind of an accident, it should probably be the same as pushing OK.

But that should only happen if you do a click in one spot, you should be able to get view manipulation if you drag the mouse instead of doing a click and release on one spot.

This should be the same behavior as V3 though, do you see any difference between V3 and V4 here?

- Michael

Hi Michael,

Ah, all viewport navigation turns out to work without cancelling the Export process if I first left-click once outside the Export dialog, activating the main interface. In V3 this wasn't necessary.

On a side note: my RMB is assigned to a side-button of my Wacom pen, but that's how I've always worked with MoI.

Today I tested my old and dusty 3d Connexion Space Navigator with MoI v4(Mac) + High Sierra 10.13.1 + 3DxWare 10 (latest). Everything works good.

Hi Max, thanks for testing the Space Navigator, I'm glad that is working again. I should be able to get to your other list sometime soon here.

- Michael

Hi Max,

>>5. I noticed a rare Orientation Picker bug. Unfortunately I don't know how to reproduce it.

Yes, i had this too...



But i can reproduce it with the attached 3dm file.

Open it - its normal but than use the CPlane tool - it start to flicker..
If you change to split view its even more flicker.
I can reproduce the flicker only with this file ...

This file was hardly tortured by a script i am working on where i also use a orientation picker..
(the script ChangeHole delete holes or change there diameter.. very beta)

I'm curious if one can reproduce it ( i`m on Mac 5k High Sierra)

Hope it helps
Ralf

Hi Ralf,

I noticed the same bug with your file. Thank you!

Hi Ralf, I can repro that over here on my Mac too (not on Windows), thanks that will help!

I had some very similar looking things during development not too long ago, which was because of a wrong index buffer being used.

- Michael

Hi Michael.

Just out of curiosity...what kind of Windows machine are you using for testing Moi V4
(hardware and software config I mean...)

Thanks.

Marco (mkdm)

Hi Marco, nothing too fancy - a few years old quad-core Core i5 and Windows 7.

I have been thinking of building a ThreadRipper machine recently but have managed to resist so far.

- Michael

Hmm.....ThreadRipper...
Coupled with a Vega 64 could be a rather affordable number crunching machine !!
Quadro cards are too, too much expensive and can't
offer excellent FP64 performance like Vega.
I have a Gtx 1080 Ti and it has "only" 480 GFLOPS in
FP64, much less than Vega, but it has 3600 cuda
and a super fast and massive 11Gb vram
and 11 TFLOPS in FP32.
For what I often do, that is GPU cuda rendering, is a bomb!


Ciao!

Hi Max & Ralf, I found the orientation picker draw bug. It was on OpenGL only, it's something that OpenGL code is rather prone to where you can't just directly map/unmap a specific buffer, you have to kind of set it as the active one first and then say "map the active buffer", but if you're not careful setting the active index buffer can also inadvertently modify the index buffer that's set in some other collection of settings as well. So then things would draw with the wrong index buffer.

It will be fixed for the next beta, just let me gather up some more fixes for 3-4 more days and I'll release a new one.

Thanks for reporting it!

- Michael

This is excellent... very happy to see V4 beta out. V4 looks much better than V3 on my MacBook and is much snappier.

I can't say enough good things about Moi3d and your support Michael. Keep up the good work!

>Thanks for reporting it!

Thanks for fixing it!!!!

Ralf

Hi Max, thanks for all your work testing your scripts!

re:
> 1. factory.setInput function stops with "Invalid function argument" error when
> an argument type is wrong. In fact it's not a MoI problem, but (if I understand
> clearly) v3 in this case just set input to null and don't stop a script.

Hmmm, well it looks like v3 and earlier didn't null out the input it just silently did nothing if the value couldn't be used.

This is one of those cases where it's kind of hard to decide to do, should it do what's probably the wrong thing since v3 did? But that might make it harder in the future for someone to find out their new script isn't doing what they thought it was... Maybe wait and see if it comes up with some more older scripts?


> 2. moi.geometryDatabase.findstyle function returns a wrong data when it creates a new style.

Yup, this was definitely a bug in moi.geometryDatabase.findstyle for the case where it creates a new one. Fixed for the next release.


> 3. Something wrong with moi.command.getOption function. I can't read data from moi.ini

I can't seem to reproduce this one over here, is it possible that the option isn't present in your Mac moi.ini file? moi.command.getOption() will throw an 'Operation failed' exception if there isn't any such option in there.


> 4. Interactive scripts perfarmance problem. MoI v4 18.11 works much faster than
> with 13.11, but still slower than MoI v3/4(Win) and v3.1(Mac).

This one is going to take me quite a bit of effort to analyze very well, so probably after the next beta I can take a look. It is possible that raw script performance has taken a hit with the 64-bit transition, but it will take some profiling to try and see what's going on. EDIT: maybe I should ask you to clarify - is it only the v4 Mac version where this is happening?


> 5. I noticed a rare Orientation Picker bug. Unfortunately I don't know how to reproduce it.

You probably already saw but this one's fixed too now for the next release.


> Unfortunately I can't find a way to show previews in Moi html windows. Neither
> native nor script paths doesn't work.

So you mean you want to make a tag that loads a file from the appdata directory? How about if I add support in the moi:// protocol handler so you could do moi://appdata/Objects/Filename.png as the URL, similar to how moi://ui and moi://commands URLs can be used currently.

Thanks,
- Michael