MyRevit file is not too big, 300mb. When I open Enscape, the view selection window will be gray and set in a default 3D view. When I open a camera view in Revit, it will launch Enscape in that view. But I couldn't select other view from drop down menu. There is no drop down menu at all!
joniliu2003 DanS I think what you mean happens only if you're in a perspective view in Revit. Before Revit version 2017.2, any plugin, Enscape too, was completely blocked when you've been in a perspective 3D view. You had to switch to a parallel 3D view or floorplan in order to control Enscape.
In the first instance, can you please make sure you're using our latest release? If that doesn't help, or you're already using Enscape 2.8, then please also send in feedback report with a link to this thread for reference in the submission form for further troubleshooting:
In order to move my course materials from Scratch to Snap I need a stable version of Snap (this is the need that makes me use still Scratch 1.4 instead of Scratch 2 or 3). My students indeed create large multimedia Scratch projects (100-300MB) with many images and sounds and they cannot risk that their project become unusable for any reason (they are not computer science majors and I would risk a stack of dead student bodies at my door).
I can start creating a fork of Snap (with just the current features) so to add with each new version just the bug fixes. In order to do this, I will need to know for each modification of a new Snap version if this modification is a bug fix or an improvement or a new feature.
Is this kind of info something that could be added in the code or in the new release notes? I know that short info about bug fixes and new features are in the new release notes, but at the moment they are too short in order to be sure that I'm not adding something that could possibly break what was previously working fine.
I can confirm that relying on browsers can cause a lot of troubles (we had a tool that created learning objects in the SCORM standard that we had to abandon as it kept crashing almost every update of Chrome/Firefox). That is why I usually freeze the PC of my labs, so that their browser is never updated.
Yes. And they are all very useful. What I was asking is, if Jens thinks it is a viable strategy, adding some more details. For example, looking at the diff I can see where the changes are, but I'm not always sure if I'm correcting a bug or I'm adding unnecessary new code that could potentially break Snap. I mean, unnecessary for me as the current Snap version is well beyond my students' needs.
I'd like a lot the idea of having a very small package, but the need of having a stable release is much more pressing. Do you have suggestions about good practises to package a frozen browser in my installation? Thanks in advance for any suggestion.
I understand that. But even having a suggestion if a change in the code is something related to a new feature of it is a bug fix of the previous version would help me a lot in maintaining my frozen version as bug-free as possible.
This is neither here nor there with respect to your request (about which I do agree with Joan that you're underestimating how much extra work you're asking Jens to take on in the press of a new release), but in the clause I quoted, I think you have a wrong view of how we develop new features. Some new features (the ones I design, I'm afraid) are addressed to advanced programmers, but others are to simplify programming so that beginners can accomplish commonly-desired tasks. An example is the 5.0 feature that allows you to drag a CSV file onto the Snap! window and have it automatically appear as a variable whose value is a list of lists. Before that feature, you had to understand the distinction between a SPLIT and a MAP of SPLIT. Now it just happens.
I'm not saying that Snap has useless new features. Not at all. Without those features -as I clarified in Heidelberg- I would never had the possibility of developing the BloP extension. It would have simply required too much time to just a single person to be developed.
But, as my students do not need new features with respect to the current Snap state, avoiding to add new features to the Snap version they use I can avoid adding new issues to my frozen version, issues that, more easily, are linked to the addition of new features.
I don't think so. Otherwise I wouldn't have asked it. But I can be wrong. I have seen a lot of places in the Snap code where I see comments saying "this fixes this bug". Usually solving a bug takes just a few lines of code. Not always. If it takes just a few lines the usual comment "this fixes this bug" could be added to the code. If not, a comment in the HYSTORY.md saying that the solution to the bug is spread in several places would be fine too. Anything would help.
I have set it so that all hot buckets only last a day, and roll straight into warm buckets. When I check a certain date of indexing volume, it may say that I have indexed 300 MB of data that day, but when I check my warm bucket (in the folders) for that date, it only has 100 MB of data.
All indexed data is not stored in 'defaultdb'. It could be that you're indexing data into other indexes. Defaultdb is the 'main' index, where data is sent if you haven't specified any other index. If you've got a custom index, data will be written to that index, and not 'defaultdb' in $SPLUNK_HOME/var/lib/splunk/. You've also got the internal indexes within Splunk, but that data shouldn't be counted by the indexing volume page.
Keep in mind that warm buckets only contain data that is not going to be written to again, so if you're looking at warm buckets that contain data for a specific time period, there could also be hot buckets that are still being written and haven't yet been rolled to warm.
It might also be possible for a person to configure index retention in such a way as to clear out data older than a certain period of time/over a certain size. If that is done, you won't be able to tell by the size of the index about the indexing volume for that day.
For these reasons, I wouldn't recommend that you use a method of looking at physical space used on disk to determine how much size is used. The page you're looking at hits the rest endpoint and that counts the totality of indexed data in non-internal indexes from midnight until the time you view the page.
How many indexes do you have configured? Do you have different paths configured for your hot, warm, cold, and frozen size? Also the raw data is compress, so the index through put may not be the same size as your volumes. What settings have you applied your index.conf? Keep in mind these are settings are applied on an index by index basis. I am figuring you configure each of your indexes with maxHotIdleSecs = 86400.
I've been dealing with this issue for months now and officially losing my mind here, there's no way I can be the only one having this issue. I feel like vie tried everything to fix the issue but nothing helps.
Basically what happens anytime I open a dialog box/ window. Like if I hit filter, override graphics in view(EOD), or rename a sheet. basically any button that would bring up a pop up window causes this to happen. Its not every time, sometimes is only 30minuties into work others 2hrs in and very very rarely ill go a hole day without it crashing.
When it freezes basically everything in the ribbon goes gray and when I click anywhere on Revit windows "chimes" as if I need to close the popup windows that should have opened. As soon as it happens one of the CPU cores goes straight to 100% and never drops until I End task and loose my work.
I also upgraded to a new laptop with a fresh install of everything, and sure enough after about a week the problem started again, and almost seems like it gets more and more common. I've been trying to catch the issue on a screen recorder but haven't managed to yet.
Is there anyway to actually contact Autodesk? I'm getting extremely tired of losing hours of work nonstop! and yes I have the save reminder set at every 15 minutes but sometimes it doesn't popup somehow and it will freeze and ill check my locally copy and its an hour old.
Right now I'm working between 2 different projects. both under 300mb and have 3-5 links. I tried unlinking everything but one link to see if anything changed but that didn't make any difference other then the project opens faster.
The only thing I do different then the others in my office is I use a 3dconections 3D mouse, but I would just be amazed how that could make Revit lockup when opening a window? And I reinstalled it and also had it one my last computer, So I feel like if I had this exact issue on 2 computers I cant be the only one. I messaged 3dconections and they haven't heard of any reports of this on there end, but they are very helpful and helping me run a diagnostic log and they are going to review it and see if its coming from the mouse.
3a8082e126