@alexpacio2013
Prefix a member's name with a @ and they are notified of the mention.
@fredo6

@alexpacio2013
Sorry, but you misunderstood what I meant.
If VertexTools was enabled but LibTT was not loading [or not installed] then that could cause some weirdness.
However, it seems that the issue is between VertexTools and LOTT clashing...

Does VertexTools need TT's Lib ?
Have you tried installing that ?

@PRONAY24
Download/install the extension.
After a while it needs licensing...
Also remember that it needs LibFredo6, SketchUcation toolset etc to work...

Why have you just posted another report-output - showing a slightly older version of LibFredo6 [which shouldn't cause an issue anyway!] and fewer installed Fredo6 extensions ?
Another computer ?
AND see how it still shows the SCFLicense directory exists, BUT the Signature File is 'absent'
Have you done anything to download, save and activate any licenses ??

@teppi_edmund

Before Rich comments... read the final line - There is a SCFLicense directory, BUT the Signature File is absent [aka missing].
Have you saved the license file[s] onto your computer is a logical location - like a subfolder in your Documents folder...
You then need to Manage and activate these...

@fjsgruppe
There are two possible places that might be tripping things up.

One is user Windows user-name - as I explained:
It doesn't follow Windows guidance as it contains an umlaut...
C:/Users/fjSchüssler
Try changing your user-name to fjSchussler or fjSchuessler ?
It needs just ASCII characters and some limited punctuation are required

Two is your computer-name [IT might need to address that].
Again, the name's characters requirement is much as stated above...

Did you try deleting all faces and then using edge.fine_faces ?

Try the user-name solution I mentioned...
PS: does the computer's name contain any non ASCII characters ?

@fjsgruppe said in fredo6 licences:

As well as doing what Rich asks, please confirm you have the latest versions of LibFredo6 [for vital helper files and our SketchUcation toolset installed [for the licensing].
And your Windows user-name doesn't follow Windows guidance as it contains an umlaut...
C:/Users/fjSchüssler
If all else fails try changing your user-name to fjSchussler or fjSchuessler ?

Collect all of the grouped edges, the use intersect to break the edges and faces...
https://ruby.sketchup.com/Sketchup/Entities.html#intersect_with-instance_method

If that doesn't work, then try adding a temporary short edge perpendicular to the faces' plane, at the non-splitting intersection which should break the crossing edges and separate the faces...
Delete the short edge afterwards...

So you have another extension loading which causes the issue !
MX
Which in turn has a Util module
which sets an object camera on
Relating to Sketchup::Page.
It then has unloading Fire data load
Resulting in 1AA Also Extended Cut
Which are all called by OnActiveModelChanged

Or to put it more simply...

You have an extension which creates a module called
MX
This adds an observer to the model
OnActiveModelChanged
This seems to run all the time - perhaps activating as the extension is loaded.
When the model changes something happens with its code as it looks at pages [scenes], and it can cause a BugSplat.

So it's not directly related to Extrude Tools at all - a 3rd party extension is hijacking your model and splatting when something happens in another extension...

Search through your extensions and find one setting up module MX - that's the real culprit.

@Mike-Amos
So to be clear...
When you use the EEbyRails and it gets to the prompt to keep or delete the original lines it splats in v24 - irrespective of which choice you make....

I've retested it and can't get the same issue - .

If you open the Ruby Console and retry the EEbyRails are there any error messages at all, before the 'splat' ?

Extrude Tools - if you select yes to delete the original lines, is it then splat free ?
I assume you refer to the native measuring tool - are you 'toggling' between guide liens and points [which will have a short guide attached] ?

@Mike-Amos
Do you have the latest version of my Extrusion Tools installed ?
If so what are you trying to do when it 'splats' ??
It shouldn't clash with anything else when it's not in use, so it seems to be something you are trying to do...
Several of its functions were superseded with the superior Fredo6 tools like CurviLoft...

@Dougmcpeek1
When you download any license file you save it onto your computer, put it in a sensible location [like a subfolder in Documents]
You do not 'open' it.
Once it's on your computer you then need to validate it within SketchUp, under the Tools submenus for that extension.

Extension RBZ files can be downloaded from our PluginStore and then installed using the Extensions > Extension Manager dialog's 'install' button.
Save it onto your computer, do not try to open it - the install it.

You will need to have the latestest SketchUcation toolset installed for the licensing, and additionally it also provides tools like Extensionstore³, which allow you to auto-install selected extensions from a dialog, sidestepping the RBZ download completely, and reminders for available updates, etc.

With Fredo6's extensions you will also need his latest LibFredo6 installing - which is a library of helpers.

After these installations restart SketchUp to sync everything.
Then do the licensing.

It works best with >=v2014
This is the oldest version I have...
SectionCutFace+_v2.6.rbz
or try this...
SectionCutFace_v6.2.rbz

This suggests that your extension's free trial period has expired.
At the moment the extension is not licensed.
You must download the license file onto your computer, then apply that license [validate] to the related extension.
You need the latest version of the extension, LibFredo6 and the SketchUcation toolset installed and SketchUp restarted to sync everything...
There are lots of help posts and so on in the forum...

After installing any updated extensions, libs and the latest SketchUcation toolset, close SketchUp and restart it again to sync everything...

Read the post before yours, it announces a update, which should fix this...