Jump to content

ThisIsntMyName

Members
  • Posts

    557
  • Joined

  • Last visited

 Content Type 

Forums

Gallery

Downloads

Tutorials

News Stories

Wiki

Community Guidelines

LSPDFR BOLO Series

GTA5 Native Database

GTA5 Native Parameters

Release Highlights

LSPDFR Mod Showcase

LML User Contributions

Everything posted by ThisIsntMyName

  1. i recommend bring the decal up closer to the door handle. As of right now, i think the words are way to low on the car.
    Just....... Stunning. Amazing work by Lt.Caine. 1000000000% 5 star
  2. yea no problem! I have seen some posts recommending making sure you have the most recent DirectX installed. I dont know if this could be a fix but i guess it is worth a try. If you already have the latest DirectX Installed, try re installing. EDIT: It seems like you have a very unique issue. I really don't know to be honest. I mean i guess the best option is to wait until the mods update. On second thought, my guess is that it has something to do with albo's Common.DLL file not being updated to RagePlguinHook 0.49.
  3. ok if the RageNativeUI boxes work then it isn't anything with your resolution. As for some mods not being compatible, if this problem started before the latest RagePluginHook update, then it shouldn't be that. I guess we can wait to see when the mods are all updated but in the meantime, ill surf the web a bit and my files and try and figure it out.
  4. hmm that is a bit of a problem. I don't know the answer off the top of my head, but i'll look into it. Also, on your question if the common.dll file will fix it, I cannot say for certain. If it happens on traffic stops to, then most likely not since the common.dll is only for albos stuff. Does the issue happen with all RageNativeUI boxes? These are the blue boxes that pop up when you are in a plugins menu. It is the one in the top left corner. "Coincidentally enough, it was roughly after I turned up the PostFX setting to allow siren lights to be brighter, but that was the only change that I made to the game at all." - if it only started after this, then this probably is the problem.
  5. Make sure to edit the post and add [RESOLVED] before the title! this way people dont come trying to help just to figure out it is already fixed. Since no one knows how you fixed it, your better off just deleting all the words in the post, and just putting "Fixed, Remove if possible". By the way, when you say remove, your talking to the administrators so they know that you want the post deleted so it doesn't take up space. PS: Next time when you want to paste in the log code, hit the little eye icon, (right next to the quote symbol), on the bar above the typing area then paste the log in there. The better way to post your log is by creating a pastebin post and then pasting the log in there, followed by copying and pasting the link to your post in your support request. Pastebin is very helpful for people who want to help you because it labels the code lines (numbers on the side). This allows them to see what line the error was on so it takes less time to find.
  6. i suggest waiting for the newest albo's common.dll so that this doesn't pop up. I mean, this doesnt effect gameplay much if it is only the error box message. All I can say again is wait for albo's latest common.dll file to be released, that way this doesn't pop up when you go on duty.
  7. dont you need to add the credits? Not meant to be mean, just checking since i am new to modding and I look at credits to find good parts. :)
  8. i guess, really depends on preference. i say something different than unmarked since it is technically marked. Pst.... You have no windows on the FPIU. Might be a little chilly when your on the highway!
  9. should probably put in [Stealth] then :) Disregard the stealth thing, just realized it says unmarked, but stealth would be better I think. also i will never understand the point of releasing a unmarked skin.
  10. did you model out the belt and utilities on it? Also how about the vest?
  11. Is the charger's WHite/Blue outline line supposed to be slanted toward the front wheel like that?
  12. Alrighty, Thanks for the quick response! Let me see if i can get it to work.
  13. So I Recently installed the new Blue lights for the Captain14 Sheriff Replacement pack, but now lights on the side are red and there are no lights in the middle. Anyone know a fix? And Also, Yes this is for every car in the Sheriff pack, not just the tahoe. @TrentMUHope I'm not disturbing you but since you mess around with the lighting stuff, do you have a solution for why this is happening?
  14. Alrighty, Thanks for the quick response though!:)
  15. yea hmm, I use that and the snow doesn't show on the ground. i have tried turning off FrameScaling with still no avail. Any other solutions or fixes for this?
  16. How did you get the snow to work?
  17. Looks Nice, Wish I Could Actually Use The Cars :(
  18. lol. i wasnt that offended by it. just at first. :)
×
×
  • Create New...