Maya :: Error / This Command Requires At Least 1 Argument(s) To Be Specified Or Selected
May 2, 2011
I opened my awesome camera projection mapping scene and all of a sudden the file doesnt work.I get a popup saying "Errors have occured while reading the scene that might result in data loss. Please check the Script Editor for details."
The Script Editor says:
file -f -new;
// Error: This command requires at least 1 argument(s) to be specified or selected; found 0. //
// untitled //
commandPort -securityWarning -name commandportDefault;
// mental ray for Maya 2011
[code].....
Anyway, I googled it and "delete the mayafolder and restart Maya, thus creating a new mayafolder automatically" came up and so I did, it didnt work. The next solution apparently was to export eveything into a new scene, but only a third of my stuff is IN the scene so that doesnt work at all (yes i tried anyway).The last thing I did in the scene before I closed it down for the weekend, was to import about 10 nCloth flags into the scene. Disabling them all ofcourse, but still, that might be the reason it's crashing, I dont know.
This morning when I started Revit 2013 and tried to open a file that I was working on last night, I got this error: "encountered an improper argument." The file will not open.
I tried to open a different file, and I get another error saying "An unrecoverable error has occured. The program will now be terminated.... " Revit will close.
I cannot open any files, or get Revit to run. Is my installation corrupt? Do I need to re-install or is it possible to try a repair?
I just bought Silver Efex pro 2 after uninstalling a pirated version my sister downloaded. When I try to edit a photo in Silver Efex 2 through Lightroom 4 a box comes up and says unexpected error performing command: bad argument #1 to lower (string expected, got nil). I am not good with computers.
Also is there any way to restore factory defaults all throughout Lightroom. Maybe doing that and reinstalling Silver Efex would work? Even when I deleted the pirated version of Silver Efex the Silver Efex still showed up in the Edit In box. I need to get that one to go away so the new Silver Efex will appear in Edit in box I guess.
Some saved files will not reopen in CoreldrawX5 showing an error message 'Encountered an improper argument' and that is it! Very frustrating as all the work seems to be lost and needs to be redone.
I activated the Poly Count from the Display Menu; but it shows the components that are in the view at the moment. I'd like to know instead if there is a way to display the number of the components selected.
I'm used to being able to select and hide polygons while creating models in programs like Lightwave and Modo. It is an essential function that I can't imagine Maya lacks, yet there isn't an obvious way to do this as far as I can tell. Is there a workaround?
So, in max there is a way to turn this off. So that when you select an object the edges are not visible. That way, when you select and object and have a look at it, you do not have to be distracted by the wire frame.
Is there a way to do this is Maya? I'd lke the geo to appear as flat shading without the wireframe visible even when I select it.The reason is, I want to select it, and work on the UV mapping. I'd like to make some changes to the map, and see how they look on the model without having to deselect the mesh each time I make a change and what to see it without the wireframe.
Where i could find those ribbon icons in max, for example am adding the export selected command which has an icon when you do file export, but when i add it to the ribbon it says missing icon, and i only have a modeling folder and object paint folder with icons.
Currently, I'm trying to get through the following lesson: [URL]........
My problem: I'm at the part where I need to make windows, this, by extruding selected subdivisions inwards, using the z axis. The problem is that the selected faces wont enter the building. In others words, the selected subdivisions wont extrude inwards, so that no recess (or window) appears. They go outward just fine, but going inward, the subdivision remains lined up with the outer face of the structure, so that no recess appear and the structures face remains flat.
Here's a few screenshots to better show what im saying:
Wireframe mode: As you'll see, the window recesses appear just fine in wireframe
My rotate tool in maya seems to be "locked" i can't freely rotate whenever i left click hold the center and it only rotates where my viewport is looking at so if im at the X axis I can't rotate the Z axis. Tried setting my preferences to default and nothing. I've also set my rotate tool to default.
Whenever I move my camera say to the Z axis the Z handle gets selected and same when I move the camera to the X axis.
If I select some objects (i.e. pipe, feature line, etc.) and right click to bring up my shortcuts, I click on SOME commands (i.e. object viewer, elevation editor, etc....respectively, the command does not progress....it forces me back to a selection box cursor and I have to reselect the object.
For example, I select a pipe, I then right click, shortcut menu pops up, I select "object viewer", and then my previous slection is not granted and it asked for a new selection (it used to always just proceed with the command), I then have to select the pipe I had previously seleted, and the command proceeds as normal.
not a bid deal, but it slowing down my productivity having to select these items twice. The wierd thing is that it is not like this with all of my right click short cut commands...only a few!?
i just installed the 2012 autocad on my laptop and everytime i use trim or rotate or anything else the screen just goes black and the computer freezes for a few seconds and then it comes back and tell me that its trying to adjust the program with the monitor but it never ends and it keeps doing the same thing. btw my laptop specs are: windows7 home premium, intel i5, 6gb ddr3, intel HD3000 graphics.
Whenever I try to select a Curve to select 'Control Vertex' I get the options for the Camera instead, the only work around I have is to Hide the Camera which also switches off the image planes, then select the curve and select 'Control Vertex, and then re-enable the image planes.
I'm currently having diffulties editing my selections, specifically lines, hatching etc through the properties command. When I select a polyline or hatch and then select properties it shows that there is no selection. However if I select text I can edit the text style, but I can't change the colour. I've tried to change back to the default settings but that hasn't work.
I've experienced a major issue with baking rigid body simulations in PhysX for Maya 2012 64-bit Hotfix 2. I'm running Windows 7 Pro 64-bit.
The simulation runs fine in the viewport, even in Viewport 2.0. The animation is a classic 10-pin bowling shot. When I try to bake, the whole thing goes haywire. Pins lean over and start dancing insanely. Not a desirable outcome.
We use Maya 2008 and 2009 here, along with Turtle 5.1. Our exporter plugin only works with 32-bit Maya, so we are a bit tied to that as well. We are using Turtle to perform shadow and AO bakes for our game, but Turtle fails unpredictably when baking large (>4096) textures. Many times I see:
// Error: Error during baking, see script editor for details! //
Of course, even with "Echo Every Command" enabled in the Script Viewer, and every output option enabled in Turtle, I get no actual error message. On a 16318x16314 bake, it completes 75% of the bake, then does nothing for the remaining 25% (while updating the progress bar) and exiting with the above message. On 8K bakes, it will seemingly finish the bake, but not write out the texture. Sometimes, Maya will crash completely, either with the usual error dialog, or just silently close without any message whatsoever.
In my experience, running out of memory on a 32-bit program can have similar results, and it is possible that 32-bit Maya even running on 64-bit Windows 7 has the same issues, but Task Manager shows only 1.5 GB used by the Maya process at the time of failure, far below the ~2 GB addressing limit for 32-bit programs.
I get an error code "file could not be moved to selected location" when trying to move an image or a folder from one hard drive to another within Lightroom.
I am migrating from a Windows-based PC to an iMac. I successfully used Lightroom to move all my images and catalogs from the PC hard file to a USB attached hard file. I was able to go to the iMac and move the Lightroom Catalog from USB attached drive to the Apple Macintosh drive. I was able to bring up Lightroom with moved Lightroom Catalog and work with all of my images. Then using Lightroom I was unable to move the images to the Macintosh hard drive without getting the error code above.
We are receving error on our VBA program under AutoCAD2011 "Invalid argument Tag in setting TagString" when writing tag string.Our lagazy program used to store some data on a hidden layer as tag string. Now the new VBA is not accepting those lines.Is it a bug or there is any workaround for this.
It was working without any trouble for AutoCAD 2005-2010 versions.Example -
My Corel X5 file won't open but gives me the message "encountered an improper argument" or just freezes trying to open it. I tried installing Corel on a different computer but with the same result.
Is my file corrupt? Is there any way to (partly) recover the inforamtion in my file?
I'm trying to create a .DLL to access a database from within iLogic. I'm new to VB.net so I'm having some trouble. I need to pass a multidimensional array as an argument to the DLL, but when I try to run the code I get an error that says "Number of indices exceeds the number of dimensions of the indexed array."
Here is my code..
The errors occur on the sData(0,i) and the sData(1,i)
I left all the database code off, because passing the array is the big issue I believe.
Public sub AddRecord(ByRef sData() As String) For i = 0 to FieldQty rst.Fields.Item(sData(0,i).Value = sData(1,i) Next End Sub
I have a user in my group that is hesitant to upgrade to 2012 because , he has many lisp routines that are associated with the PREVIOUS selection feature. This selection is very useful in that when you are moving or selecting many objects you can enter P for previous and the object will be selected.
In 2009, when you select objects then hit escape, then try to execute a command requesting to use the Previous, AutoCAD will remember the last selected object and then highlight it.
In 2012, when you select objects then hit escape, then try to execute a command using P for previous, it will not highlight the previous object selected but will highlight the previous object where a command was executed on.
Hope I haven't lost you. It seems there should be a setting under SELECTION of how to manipulate the Previous selection feature.
In attempting to follow a YouTube tutorial, working on a cone shape in vertex mode, when I select a single or row of vertexes, all vertexes get selected. When this happens, I note the coloring ranges from yellow at the selection point(s) graduating to black furthest away.
From this, I assume I have some other parameter/ mode invoked which I am unaware of.
I am trying to import a DWG from AutoCad 2010 (PC) into Maya 2013. All I get is an error. I was searching trough the web and have found no solution to this.
I am getting some crazy normals when I try to import an FBX file. The meshes I'm trying to bring in end up looking disjointed. I can go through and manually delete each polygon and then fill in the hole, and it looks fine, but I certainly don't want to have to do that for thousands of polygons in each model. I've had this happen with every FBX I've tried to import. How I can make these look smooth again? I've attached a picture to show what I mean.
I've tried re-creating the UVs with planar and automatic mapping, but it didn't work.
Usually I only use Edit Mode in X4.Recently I have been exploring Manage Mode and now decided to try Adjust Mode.I have found that everytime I leave Adjust Mode to go to Edit Mode or Manage ModeI get an error "Encountered an improper argument".
