While not as helpful, what I have done is created my own “Mouse” object using the Camera and UserInputService. It works very similarly, but would allow me to add any number of instances to an ignore table, since it uses raycasting.
If you want, I can paste that code. It’s a standalone module. I imagine you’d be able to figure out how to do it regardless.
Of course, having this done C-side would be best I would assume, thus I agree with you. It would be cool to see this added to the Mouse.
If you’re offering to give me what you’re currently using which would save me the trouble of having to do it myself, then I’m not going to decline your offer. It’d be much appreciated if you provided that, and I’m sure I won’t be the only one who would use it. Unfortunately, I won’t be able to use it with what I’m working on right now because the goal is to add certain items to the TargetFilter and have the default studio tools ignore these items, but until we’re able to officially add items to the target filter, I’d be able to use this a bit elsewhere.
Cool. I’m at work right now (on break). I’ll post it here when I get home. Only working half-day today so It’ll be in a couple hours.
Or just make TargetFilter take a table as well… problems solved
Personally, I’d prefer a table to store the target instances.
Or, going with the original idea, I’d say that there should definitely be a method to clear all target filters.
[300th post :D]
It would be. mouse:GetTargetFilter() would return a table.
local targetFilter = mouse:GetTargetFilter()
for i=#targetFilter,1,-1 do
mouse:RemoveFromTargetFilter(targetFilter[i])
endor
local targetFilter = mouse:GetTargetFilter()
while #targetFilter > 0 do
mouse:RemoveFromTargetFilter(targetFilter[1])
endThe whole point in not adding an official method for clearing the entire target filter is because you probably shouldn’t be doing that. You’d be overwriting what other plugins / scripts added to the target filter, effectively breaking them in some way. If you need to clear the target filter and you’re not using a plugin and only using scripts you made, then it’s not that hard to clear it manually.
I’d write up an API proposal for this but I know that it would be instantly shut down because the Mouse object is all but deprecated at this point.
EDIT: In favor of things like UIS, CAS, and Raycasting.
but none of those have the current target of the mouse or the current location of the mouse in the worldspace 
UIS would be the only one of the three to have those two things, and it doesn’t have a table target filter either (it doesn’t have a target filter to begin with because there’s no reason for it to, but I’d assume the ROBLOX engineers would just stick with what they have and use the same object target filter that they use in the current mouse if they were to add mouse.Hit/Target to UIS).
I think UIS should have a readable MousePosition property.
If that were added would you be able to just use raycasting?
Mouse module:
local mouse = require(mouseModule).new()
-- Methods:
local screenPos, delta = mouse:GetPosition()
local isDown = mouse:IsDown(UserInputType button)
local cframeHit, target, surfaceNormal = mouse:ProjectMouseRay(table ignoreList)
-- Events:
mouse.ButtonDown(UserInputType button)
mouse.ButtonUp(UserInputType button)
mouse.Moved(Vector2 position, Vector2 deltaPosition)
mouse.Scrolled(Integer delta)Module code:
-- Mouse
-- Crazyman32
-- April 28, 2015
--[[
Usage:
local mouse = require(thisModule).new()
METHODS:
<Vector2 position, Vector2 delta> mouse:GetPosition()
<Boolean isDown> mouse:IsDown(UserInputType button)
<CFrame cframe, Object target, Vector3 normal> mouse:ProjectMouseRay(table ignoreList)
EVENTS:
mouse.ButtonDown(UserInputType button)
mouse.ButtonUp(UserInputType button)
mouse.Moved(Vector2 position, Vector2 deltaPosition)
mouse.Scrolled(Integer delta)
--]]
local Mouse = {}
Mouse.__index = Mouse
function Mouse.new()
local player = game.Players.LocalPlayer
assert(player, "Could not get player")
local cam = game.Workspace.CurrentCamera
local Ray = Ray.new
local input = game:GetService("UserInputService")
local button1 = Enum.UserInputType.MouseButton1
local button2 = Enum.UserInputType.MouseButton2
local button3 = Enum.UserInputType.MouseButton3
local mouseMovement = Enum.UserInputType.MouseMovement
local mouseWheel = Enum.UserInputType.MouseWheel
local mouse = {}
local mousePos, mouseDelta = Vector2.new(), Vector2.new()
local clicking = {
[button1] = false;
[button2] = false;
[button3] = false;
}
local function CreateEvent(eventName)
local e = Instance.new("BindableEvent")
mouse[eventName] = e.Event
return function(...)
e:Fire(...)
end
end
-- Events ---------------------------------------------------------------
local buttonDown = CreateEvent("ButtonDown")
local buttonUp = CreateEvent("ButtonUp")
local moved = CreateEvent("Moved")
local scrolled = CreateEvent("Scrolled")
-------------------------------------------------------------------------
-- API ------------------------------------------------------------------
function mouse:IsDown(inputType)
return (clicking[inputType] == true)
end
function mouse:GetPosition()
return mousePos, mouseDelta
end
function mouse:ProjectMouseRay(ignoreList)
local pos = self:GetPosition()
local ray = cam:ScreenPointToRay(pos.X, pos.Y, 0)
ray = Ray(ray.Origin, (ray.Unit.Direction * 999))
local hit, hitPos, normal = game.Workspace:FindPartOnRayWithIgnoreList(ray, ignoreList or {}, true, false)
local cframe = CFrame.new(hitPos, (hitPos + ray.Unit.Direction))
return cframe, hit, normal
end
-------------------------------------------------------------------------
-- UserInputService Setup -----------------------------------------------
local function InputBegan(inputObject, gameProcessed)
if (gameProcessed) then return end
local inputType = inputObject.UserInputType
if (inputType == button1 or inputType == button2 or inputType == button3) then
clicking[inputType] = true
buttonDown(inputType)
end
end
local function InputChanged(inputObject, gameProcessed)
--if (gameProcessed) then return end
local inputType = inputObject.UserInputType
if (inputType == mouseMovement) then
local newMousePos = Vector2.new(inputObject.Position.X, inputObject.Position.Y)
local delta = newMousePos - mousePos
mousePos = newMousePos
mouseDelta = Vector2.new(delta.X, delta.Y)
moved(mousePos, mouseDelta)
elseif (inputType == mouseWheel) then
local num = inputObject.Position.Z
scrolled(num < 0 and -1 or num > 0 and 1 or 0)
end
end
local function InputEnded(inputObject, gameProcessed)
--if (gameProcessed) then return end
local inputType = inputObject.UserInputType
if (inputType == button1 or inputType == button2 or inputType == button3) then
clicking[inputType] = false
buttonUp(inputType)
end
end
input.InputBegan:connect(InputBegan)
input.InputChanged:connect(InputChanged)
input.InputEnded:connect(InputEnded)
-------------------------------------------------------------------------
return setmetatable(mouse, Mouse)
end
function Mouse:__tostring()
local pos = self:GetPosition()
return ("Mouse <" .. tostring(pos) .. ">")
end
return MouseNote: This works, but it is still a work in progress. I have a Keyboard module that is similar like this, thus eliminating any need for the Mouse object. Let me know of any issues you find, so that I can continue to fine-tune it.
[code]
local mousePosition = Vector2.new()
local function inputChanged(input)
if input.UserInputType == Enum.UserInputType.MouseMovement then
mousePosition = Vector2.new(input.Position.X, input.Position.Y)
end
end
function script.GetMousePosition.OnInvoke()
return mousePosition
end[/code]
Extending this to add a 3D mouse position that uses a custom raycast would not be hard. Just toss this in a local script and call it your mouse.
EDIT: Ninja’d
[quote] [code]
local mousePosition = Vector2.new()
local function inputChanged(input)
if input.UserInputType == Enum.UserInputType.MouseMovement then
mousePosition = Vector2.new(input.Position.X, input.Position.Y)
end
end
function script.GetMousePosition.OnInvoke()
return mousePosition
end[/code]
Extending this to add a 3D mouse position that uses a custom raycast would not be hard. Just toss this in a local script and call it your mouse.
EDIT: Ninja’d [/quote]
This is awful. Are you telling me that all my scripts that want to pull the mouse position should connect to this? Such a basic feature should be exposed through UIS.
@Ethan and Davidii: How will that work in this situation:
I have collision boxes for certain models. I have a plugin that auto-generates them for certain models, and auto-resizes them when the scale of the model changes. I want to add the collision boxes to the target filter so the default studio tools, CmdUtl, and every other building plugin I use ignores those parts like they don’t exist so I can transform the model at will. I can’t modify the default studio tools, and I would prefer not to fork my own version of all of my building plugins, unsubscribing from future updates.
Let’s say I also want to filter the invisible parts that contain lights from being selected. I don’t want to be able to select them unless toggle markers on and click the marker, but even with the markers off I still want the light to affect the world (which means I have to have a part in the world to contain the light). I’d have to have some sort of target filter to add those lights to.
I agree with the principle behind what Ethan is saying in the sense that something commonly used should be in the API. Remember that workspace:GetGravity() that you requested a while ago? Even though it was easy to remember 9.81*20, you thought it should be in the API because of how frequently it’d be used for gravity scripts. Same principle here.
Though, I’d still need a target filter for the two scenarios mentioned above. GetMousePosition wouldn’t work for me.
[quote] @Ethan and Davidii: How will that work in this situation:
I have collision boxes for certain models. I have a plugin that auto-generates them for certain models, and auto-resizes them when the scale of the model changes. I want to add the collision boxes to the target filter so the default studio tools, CmdUtl, and every other building plugin I use ignores those parts like they don’t exist so I can transform the model at will. I can’t modify the default studio tools, and I would prefer not to fork my own version of all of my building plugins, unsubscribing from future updates.
Let’s say I also want to filter the invisible parts that contain lights from being selected. I don’t want to be able to select them unless toggle markers on and click the marker, but even with the markers off I still want the light to affect the world (which means I have to have a part in the world to contain the light). I’d have to have some sort of target filter to add those lights to.
I agree with the principle behind what Ethan is saying in the sense that something commonly used should be in the API. Remember that workspace:GetGravity() that you requested a while ago? Even though it was easy to remember 9.81*20, you thought it should be in the API because of how frequently it’d be used for gravity scripts. Same principle here.
Though, I’d still need a target filter for the two scenarios mentioned above. GetMousePosition wouldn’t work for me.[/quote]
Raeg, you said it was just needless API bloat. Why in the world are you using it as a positive example now?
I pointed that out to make you remember why adding frequently used things to the API is a good thing. The reason I called it a waste is because it was just so easy to remember. It would have been one thing if we could set it or ROBLOX changed it over time or something, but it’s completely static. If you’re programming something that involves gravity, there’s an extremely high chance you know the gravitational constant 9.81 m/s^2 because that’s common knowledge that you need to know if you ever want to work with gravity in life. The only thing that you might not know is the 20 studs = 1 meter in ROBLOX. I wouldn’t add static gravity as a property for the same reason I wouldn’t create a static property called “StudsPerMeter” in ROBLOX and for the same reason I wouldn’t add Enum.Symmetric.ResizeIncrement (assuming that was possible with enums of course).
yessss please add this.
I really need this right now. I don’t see any reason to not add it and my game is getting messy having to place parts the mouse should ignore in one model. Please reconsider this.
I would recommend using a custom mouse module, it gives better control over the mouse with the same functionality. If you don’t want to write your own then I highly recommend using EgoMoose’s module in place of the default mouse, and switching to this module is fairly straightforward.
Roblox hasn’t officially deprecated the old mouse stuff but all of the functionality exists in other parts of the engine to essentially 1:1 recreate the functionality of the old mouse, with better/more custom tailored functionality.
That’s nice and all but I’d really rather just have this functionality in the mouse by default. I’d love for Roblox to update the old mouse instead of making me rely on modules and stuff for such basic features.
That’s a decent solution for now, I guess (Although it’s still cluttering my game).