Jump to content

Search the Community

Showing results for tags 'Editor'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Introduce Yourself
    • Showcase and WIP
  • ProBuilder
    • General Discussion
    • Bug Reports
    • Feature Requests
    • Extensions
    • Tutorial Requests
    • ProBuilder Contests
    • ProBuilderVR
  • Polybrush
    • Feature Requests
    • General Discussion
  • ProCore Utility Tools
    • ProGrids
    • ProGroups
    • QuickBrush
    • QuickEdit
    • QuickDecals
  • GILES (Generic In-Game Level Editing System)
    • Feature Requests
    • General Discussion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Sooran

    Editor breaking error

    I pasted the critical error below. I'm wondering where to start with this. Details: 1) I own the whole probuilder bundle. I have builder, grids, groups imported: 2) Barely used it much yet. A few meshes.3) Windows 10. Unity 2017.1.0b6. This is an advanced beta. NEEDED a new feature. Perhaps my Unity version could be compounding the problem?4) Editor breaking error on repeat. Reimports don't fix. Can't use that scene now :/ The error below: NullReferenceException: Object reference not set to an instance of an object ProBuilder2.EditorCommon.pb_Editor.OnGUI () System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222) Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation. System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:232) System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MethodBase.cs:115) UnityEditor.HostView.Invoke (System.String methodName, System.Object obj) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:272) UnityEditor.HostView.Invoke (System.String methodName) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:265) UnityEditor.HostView.InvokeOnGUI (Rect onGUIPosition) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:232) UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
  2. Hey all, Tool - 1) ProBuilder Advanced 2.9.0f3 Issue - 2) Having serious fps lag in the editor after opening the ProBuilder window even with nothing in the scene. System - 3) Windows 10 up to date 3930k CPU 16gb Ram 780ti Classified - Latest Drivers (checked @ 3.25pm) - Temps 40C Unity Version - 5.6.1f1 Personal Issue Detail - 4/5) I have been having this problem since first installing unity on my home computer (works fine at uni). I open up a new project and everything is running smoothly and there is no lag in the scene at all when moving about. I then import ProBuilder Advanced and once I have imported everything there are still no issues. I then click tools>probuilder>probuilder window and once that opens and I try and move even the view in the scene editor around I have serious fps issues. As shown in the video below. This happens regardless of it being a new or existing project and even when I use a project that was working fine at uni. Video 6) Video Link Thanks, Zucchini
  3. Name of tool: Pro Core Bundle (specifically ProBuilder and QuickEdit) A brief description of the issue: Warnings and an exception are outputted when building project from scratch Your system environment (Operating system, version of Unity, version of tool) Mac OS Sierra 10.12.4 Unity 5.6.0f3 Pro Core Bundle 1.0.55 Full description of issue Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Assembly-CSharp-Editor' or one of its dependencies. The system cannot find the file specified. File name: 'Assembly-CSharp-Editor' at System.AppDomain.Load (System.String assemblyString, System.Security.Policy.Evidence assemblySecurity, Boolean refonly) [0x00037] in /Users/builduser/buildslave/mono/build/mcs/class/corlib/System/AppDomain.cs:746 at System.AppDomain.Load (System.String assemblyString) [0x00000] in /Users/builduser/buildslave/mono/build/mcs/class/corlib/System/AppDomain.cs:728 at (wrapper remoting-invoke-with-check) System.AppDomain:Load (string) at System.Reflection.Assembly.Load (System.String assemblyString) [0x00000] in /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/Assembly.cs:576 at ProBuilder2.EditorCommon.pb_ProGrids_Interface.GetProGridsType () [0x00000] in <filename unknown>:0 at ProBuilder2.EditorCommon.pb_ProGrids_Interface..cctor () [0x00000] in <filename unknown>:0 UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes() Warnings: Use of UNITY_MATRIX_MV is detected. To transform a vertex into view space, consider using UnityObjectToViewPos for better performance. From: Assets/ProCore/ProBuilder/Shader/pb_FaceHighlight.shader Assets/ProCore/ProBuilder/Shader/pb_VertexPicker.shader Assets/ProCore/ProBuilder/Shader/pb_VertexShader.shader Assets/ProCore/QuickEdit/Shader/qe_FaceShader.shader Assets/ProCore/QuickEdit/Shader/qe_VertexShader.shader List of steps, clearly explaining how to replicate the issue Import Pro Core Bundle and expand all the tools into an empty Unity project Warnings and exception are outputted each time the assets are built from scratch (or re-imported via Assets->Re-Import All)
  4. 1) ProBuilder Advanced 2) Buttons in editor window are either completely black or barely visible 3) Windows 10, Unity 5.5.2p4, ProBuilder Advanced 2.7.0f7 4) Not much more to say here, buttons are either completely black rectangles or have dark-grey background with barely visible gray letters 5) All i did is update ProBuilder from asset store after like 2 months of not using it and launched Editor 6) Other than saying, that tool is unusable at this state, theres nothing much i can add. Sending a screenshoot as an attachment
  5. I'm using Pro Builder Basic and found an issue when creating corners. I've tried searching the forums for a solution but without much success. Steps to reproduce: Starting with a basic ProBuilder cube I extruded one face out to the side And then extruded the face upward again, which causes the 'gap' to appear. From what I can tell, there isn't any actual gap in the mesh. I've played around with the lighting settings some with no success either. The light that I'm using is the default directional light that Unity makes for a new scene. Operating System: Windows 10 Home Unity Version: 5.4.1f1 Personal ProBuilder Basic Version: 2.6.1f0
  6. superdupergc

    CustomAction doesn't compile

    So once you remove the #ifdef, CustomAction doesn't compile with a weird error about the ctor expecting != 2 arguments, so i added another one (it's for the tooltip) and that fixed it static readonly pb_TooltipContent _tooltip = new pb_TooltipContent ( "Set Double-Sided", "Adds another face to the back of the selected faces.", "??" ); This was the newest version off the unity asset store
×