This is certainly more disappointing then i could have imagined.

Having waded through the sales patter on the page:

@unknownuser said:

Best of all: we’re using this opportunity to challenge ourselves to earn your business every single day by constantly improving the tools you need and love throughout each year.

@unknownuser said:

This shift in our business will keep us accountable to retain your business, by releasing new features as often as possible. We are proud to take on this challenge and move our process from an annual update cycle

These statements personally offend me.
Surely a subscription license, where you are unable to continue using the software if you don't renew every year, is the exact opposite of keeping them accountable to retain our business?

I think we can all agree that Ruby would be the single most significant addition to LO, but apart from that, isn't it interesting to see how many of the other common requests people are making could be so easily incorporated?

There seems to be very little missing from LO in terms of core functionality, but so much to be gained from tweaking, streamlining, and bringing tools and processes into line with how they operate in SU.

The release of SU 2015 has filled me with optimism. My fingers are certainly crossed for an awesome LO 2016...

I'd really like to see a more user friendly approach to layers.

It'd be nice to work the same way that i do in SU, where i keep a default layer active at all times and assign entities to the layer i want them on as i create them. AFAIK the only way to change an object's layer is with this process:
select item > change active layer > move items to current layer > change active layer back.
This seems unacceptably clunky to me. (Please tell me if i am missing a trick here).

This is considerably exasperated by the fact that copied items loose their layer status and appear on the active layer when pasted.
I've become quite accustomed to the use of stacked viewports to achieve different lineweights / colours, and it always seems unforgivably cruel to me that i can't set up a stack of viewports ordered how i want them and then copy and paste them around the drawing, so that all i need to do is change the scenes.
Likewise it would be nice if scrapbook items appeared on the layers they were saved on.

I remember reading a post a year or two ago that summed up these (and a few other points) very well. I'll see if i can dig it out.

It's more geared to textures in general, but http://www.turbosquid.com is always worth a shout...

Hi,
I've just made the change from using su 8 with snow leopard to running 2013 pro on mavericks.
As with many other people, i'm finding it hard not to be a little underwhelmed with 2013 in general, but i'm pinning my hopes on some awesome improvements for the 2014 release, and looking forward to getting solid and reliable LO performance, particularly with regards to the slightly offset snapping/dimensions which plagued my work in the previous version.
At the moment, i've only got as far a opening the program, and rearranging everything how i had it before, but already i'm having problems with the toolbars/drawers.
Just wondering if i'm on my own here of if anyone else is having the same trouble...
I have a 13" mbp, so i'm limited on screen space, and when running LO3, i was able to stack the drawers together and just minimise or maximise them as required without it being a big deal, but i'm finding with my new setup when drawers are stacked together, if i maximise one, it appears behind the remaining stack, needing another click to bring it to the front, and maximising or minimising other drawers confuses the order and prevents them from sticking together like they always used to before.
I've attached some screenshots to try and show what's happening.
If this is going to keep happening, it is going to pose a serious problem to my workflow, so i'm just wondering if i'm the only one experiencing this, or if it is a known LO issue, or if it relates to Mavericks rather then LO.
Any advice would be appreciated.
Thanks,
Trev

A bit late to the party i know, but i just wanted to put a vote in for my corsair M95 as the ultimate pointing device.

http://www.corsair.com/en/gaming-peripherals/gaming-mice/vengeance-m95-performance-mmo-and-rts-laser-gaming-mouse-gunmetal-black.html

With 15 assignable buttons at my fingertips, this thing has increased my workflow a lot.

It's very well built with an aluminium chassis, tons of thumb buttons (which i like, and find very easy to reach), has a chunky scroll wheel (with just one click - i've had Logitechs in the past where the thumb wheel clicks side to side, making the central click harder to get).
It's not wireless, which i like since the signal never drops out and i never have to worry about battery life, but has a long and nice quality braided usb cord.

The only downside is that it has no native mac support, and neither usb overdrive nor steermouse will give it full functionality (didn't have any joy with controller mate, but tbh i didn't really fully fathom out the software).

Luckily the device has onboard memory, so i was able to program it with single key or key combinations from my wife's pc, and it all worked great on my mac. Obviously i can't profile for different applications, but i've been able to get the functionality i need in SU, LO, Draftsight and Chrome by adjusting the shortcuts in the software to suit.

Hi Mike,
I've been thinking about using Air display like this for a while. Unfortunately i don't have a tablet so i can't test it for myself, but i was wondering what opportunity there is to take advantage of the touchscreen functionality.
With my 13" MBP i quickly run out of space for toolbars and trays, and i've been wondering if i could park them all on a tablet, and select tools, control layers, scenes and styles etc by touching the screen. If i knew for sure that this was possible i'd probably go out and buy a tablet tomorrow. Have you tried anything like it with your set up? Is there a reason why it wouldn't work?

Hi,

I hope this is in the right place for feature requests.
I wanted to add it over in the google group, but it looks like that boat sailed a long time ago.
I've recently been using LO quite a lot to produce some construction documents for work. Firstly i'd have to say how good LO is compared to the bad old days of v2 and before...

Anyways, i've been using the workflow of stacking up scenes in viewports to achieve different line weights and colours etc., and suffering from all the usual niggles associated with LO layers, such as having to constantly change the active layer, having items or stacks that are copied losing their original layer status etc.

Then it occurred to me. What if the developers were to consider accessing the SU layer structure in LO. Instead of the sometimes cumbersome process of stacking viewports (although this could still be done if necessary/desired) - people could simply set up one viewport, and assign different styles to different layers.
This would introduce other possibilities, such as triggering layer visibility from within LO (not really a big issue for me, but i've heard plenty of others mention it). The SU layers could either be integrated into the LO layer structure (this would probably be hard to implement), or remain a separate control accessed via the Sketchup model tray.

I've seen plenty of feature suggestions that i agree with (automatic page numbering, spreadsheets, separate select/move etc.), but i haven't come across anything similar to this.
So i thought it might be worth putting out there...
Apologies if this has already been covered elsewhere.

Hi,
I found this thread because i have the QL helper issue too. I've tried the ql manage steps listed above. I can't say for sure if .skp is the only thing that makes ql go nuts, but there's no doubt that it is a trigger. I've never come across anything like the quicklook generator posted above, will it help specifically with this problem, or is it more just for being able to view files before opening them? Where should i put the .qlgenerator file? I'm afraid i'm not too experienced with this stuff...