Gamesnert

Let's just say admin WAS alright indeed, but the nightly/1.0 version got errors/warnings. I guess I might try to fix admin2 up a bit sometime soon, although my planning is overflowing with rubbish. D:

Unless you have a dynamic IP, iirc.

In the upper-right drop-down box, select the "New issues" project.

Instead of this detachTrailerFromVehicle(truck,source) do this cancelEvent() Does that solve the issue?

bindKey

Make a new resource with these models and start it while the editor is running.

And I may hope you didn't try to use the old admin, as the old admin indeed had this problem. Use the one delivered with 1.0.

Bingo, but you can just add this to your ACL.xml instead of complete reinstall: <group name="raceACLGroup"> <acl name="Default"/> <acl name="raceACL"/> <object name="resource.race"/> </group> <acl name="raceACL"> <right name="general.ModifyOtherObjects" access="true"/> <right name="function.xmlLoadFile" access="true"/> <right name="function.startResource" access="true"/> <right name="function.stopResource" access="true"/> <right name="function.restartResource" access="true"/> </acl>

Did you use MTA DP2.3 before? (you know, previous version of MTA SA) If so, did you install MTA 1.0 right over it? If so, go to "\MTA" and delete net.dll Then, try installing MTA 1.0 again. I really can't be more specific. =/

Oh you mean in freeroam? 1. Go to your server resources folder (*MTA INSTALL DIRECTORY*\server\mods\deathmatch\resources) 2. Open the freeroam resource 3. Open the meta.xml and scroll all the way down Now, you should see these options: ... <setting name="*weapons/disallowed" value="[[38]]" /> ... <setting name="*vehicles/disallowed" value="[[432]]" /> Change those to: ... <setting name="*weapons/disallowed" value="[[]]" /> ... <setting name="*vehicles/disallowed" value="[[]]" /> Should work.

I mean setPedControlState. setTimer ( setPedControlState, 200, 0, source, "aim_weapon", true )

Perhaps it's a good idea to toggle control "aim_weapon" too.

Did you install 1.0 right over DP2.3 perhaps? It might be that, for some reason, you still have the DP2.3 net.dll? If you did, create a backup folder, put your net.dll in it and try reinstalling again. It might perhaps help?

I've always had bad experiences with wireless and have heard plenty with the same. Can you just see if connecting directly with a wire to your router (if possible) does you any good?

Overall, it's not extremely hard. You just need to use the function of which I think it has the longest name of em all, and some playing with matrices. - getElementDistanceFromCentreOfMassToBaseOfModel - getElementMatrix Here's what you should do: Use the long function to calculate the distance from the center to the ground. Since it calculates from the center, the distance to the top should be exactly the same. Then, we use getElementMatrix with a slightly modified version of one of the examples on the page: function getPositionFromElementAtOffset(element,x,y,z) if not x or not y or not z then return false end local matrix = getElementMatrix ( element ) local offX = x * matrix[1][1] + y * matrix[2][1] + z * matrix[3][1] + matrix[4][1] local offY = x * matrix[1][2] + y * matrix[2][2] + z * matrix[3][2] + matrix[4][2] local offZ = x * matrix[1][3] + y * matrix[2][3] + z * matrix[3][3] + matrix[4][3] return offX, offY, offZ end Fill in x and y as 0, and z as the distance from the center to the base. In this way, you should have the position above the element. If you want it to be higher up than just the roof, you can always just increase z to get a higher point above the element. This should help you out I hope. Just do note that this is client-side only.

https://community.multitheftauto.com/index.php?p= ... ils&id=124 You might want to take that resource as a whole.

Besides that, the original scoreboard indeed had this column system, but it also just placed the columns in front of the ping by default. Which dxscoreboard does not and I'm pointing out.

The script from the second video seems to be almost perfect. Only 1 problem: He just rotates in the opposite direction. So I think this will pretty much solve your problem: local plr = getLocalPlayer(); local PEDEK function greetingHandler ( ped ) PEDEK = ped outputChatBox ( "działa" ) addEventHandler( "onClientRender", getRootElement(), firenow) end addEvent( "onGreeting", true ) addEventHandler( "onGreeting", getRootElement(), greetingHandler ) function firenow() local x, y, z = getElementPosition( plr ); local X, Y = 0, 0; local px, py, pz = getElementPosition( PEDEK ); X = math.abs( x - px ); Y = math.abs( y - py ); faceMe = math.deg( math.atan2( Y , X ) ); --faceMe = ( 360 - math.deg ( math.atan2 ( ( px - x ), ( py - y ) ) ) ) % 360 if ( x >= px ) and ( y > py ) then -- north-east faceMe = 90 - faceMe elseif ( x <= px ) and ( y > py ) then -- north-west faceMe = 270 + faceMe elseif ( x >= px ) and ( y <= py ) then -- south-east faceMe = 90 + faceMe elseif ( x < px ) and ( y <= py ) then -- south-west faceMe = 270 - faceMe end --guiSetText( label, tostring( faceMe ) ); setPedRotation( PEDEK, 360-faceMe ); -- 360-rotation makes the ped rotation exactly opposite; which appears to be just what you need setPedLookAt( PEDEK, x, y, z + .5 ); setPedAimTarget ( PEDEK, x, y, z ) setPedControlState( PEDEK, "fire", true) end

Yes.

I've found one slight problem: When adding columns, they automatically get behind the ping column. They should be in front.

Only vars in different resources or defined with "local" aren't shared. I'm pretty much sure of that yes.

User Track Player works fine, I use it every day. Skipping tracks though is a whole different story. This key doesn't appear to work yet.

Yup Script 1: a=5 Script 2: outputDebugString(tostring(a)) Output:

It's easy to get them in another server-side script. Synching client-side though can pretty much only be done with triggerClientEvent/triggerServerEvent or setElementData. (imagine the bandwidth usage if every single var that has changed was synched )

https://wiki.multitheftauto.com/index.php?title=Modules/SebasIRC This is an IRC module for 1.0. Unfortunately, it kind of sucks up your CPU at the moment.