Log in to reply
 

OpenIV 2.9



  • @meimeiriver this is not caused by OpenIV, because when you update OpenIV it does not affect ANY files in your game or mods.



  • @GooD-NTS said in OpenIV 2.9:

    @meimeiriver this is not caused by OpenIV, because when you update OpenIV it does not affect ANY files in your game or mods.

    True. But I figured maybe some mods may no longer work well together with the new asiloader (if there even was a new one). Maybe I should disable openCamera too, as I just realized I had enabled that.



  • @meimeiriver No, nothing like that.



  • @GooD-NTS said in OpenIV 2.9:

    @meimeiriver No, nothing like that.

    Why, I need to look elsewhere then. :) Thanks.



  • P.S. If only Rock* had an error log that was even half-way descriptive. Grrr.



  • I think it's TheCharacterVehicleMod again. Yesterday it was the cause of an immediate crash when I spawned into a motorcycle, over and over again. So, I disabled it, in-game; and no more immediate crashes when mounting the bike. Even in its inactive state, I think it's still doing something. Removed it altogether, and no more crashing. I really may need to let go of that mod.



  • @GooD-NTS why OpenIv still not allow to modif embeded texture ? will it be possible one day ?



  • @Shaezbreizh You actually can edit embedded textures through OpenIV using openFormats the same way it shown in

    . Also, we have Embedded Texture Editor in our roadmap, it was originally planed for 2.9 but it was postponed to the next version.



  • @GooD-NTS Well in fact I already know how to change them,
    it's just i've build a lot of landscape object and made the bullshit to use different rock texture to see the different render IG but now i'm lazy to redo them one by one via other program than OpenIv since there is a lot of object to change the texture xD

    So i was thinking to something as fast than for external texture where we can simply remplace a texture by an other in OpenIV.

    But if that in the todo list then it's cool, i can wait, good luck then ;)



  • @GooD-NTS There seems to be a problem with the new text editor. If you are in full-screen, you cannot close or minimise it, the controls don't respond.

    If you restore it to normal view, you can close it but lose the minimise option... it completely disappears from the window.

    This is on Windows 10.



  • @LeeC2202 No problems here, Win 10 too.



  • @AHK1221 The controls missing in normal view was just me being blind... the controls not working in full-screen, definitely a problem, here at least.

    Edit: That's my rolled back v678 if you're curious about the dlclist missing a load of entries... I have three different states of GTAV installed in Windows across 2 OS installs. Proves really useful for testing purposes... shouldn't be a game version problem though I wouldn't have thought. :\



  • @GooD-NTS about the addonprops " def_props.ytyp " build with @Method tool i got the following error errorcode : plNotSupportedType , anyway to solve this or is it comming from propeditor tool ?
    I've been able to open it with metatool kit from gtaforums but everyname are hash while with openIv, the name are propname. could it be the reason ?



  • @LeeC2202 will be fixed in next update.



  • @Shaezbreizh can you send me this file?



  • @Shaezbreizh got your file. The issue here is the tool which created this file. By some mysterious reason this tool writes unused types into into file. Those types are not related to maps and OpenIV currently does not support them, that is why you can't open it.



  • @GooD-NTS yeah that what i thought, then I hope @Meth0d will fix that cause his tool is really great for adding props ;S
    thank for your time



  • alt text

    Maintenance update is available for OpenIV 2.9.
    Bug fixes, new languages, setup updated.



  • alt text

    Today we are releasing quite big maintenance update for OpenIV 2.9.
    This update contain important fixes but no new features or notable changes.
    If evrething will goes well with this update we will start working on next feature update for OpenIV this week.



  • @GooD-NTS Thanks man, and do you guys have plans to add Open Formats retro-compatibility to import older versions?





  • @GooD-NTS While you're at it, can you fix this?!

    These are totally valid ytyp files, btw; but OpenIV can't deal with them. The only way to have OpenIV open them, is to take an ingame ytyp file (like from mpheist or something), open it, paste the decrypted text of the ytyp file in question into it, press Save, and the rename it to the ytyp file you wanted.



  • @meimeiriver this ytyp is made by MetaTool (or tool that based on it code). The MetaTool is writing files incorrect (it add unused types into declaration), OpenIV is unable to open those files because it does not support those types yet. There is nothing I can do. There is no reason to you to use MetaTool because OpenIV implements YMAP/YTYP support better.



  • @GooD-NTS it's related to people that are using prop editor from method that was created before OpenIv make us able to read that kind of file.
    It permit to build this file ( for addonprops ) in an easy and fast way.

    The only convenient is that instead of getting name of prop once the file is rebuild, we got hash code (when opening the file with metatool since openIv can't), wich must also be the reason we can't open it with your new feature.
    Would be really a good thing to get a compatibilty fix to edit this file with OpenIV cause prop editor is a nice and usefull tool but miss some function that we could add ourself if only OpenIv was able to convert it ;S (it's just hardcore to find wich hash is wich prop for big addonprop )
    Or may OpenIv team could release a such program with all possible function.
    I talked of that to method but unfortunatly he don't feel to redo all the program now ;S



  • @Shaezbreizh said in OpenIV 2.9:

    @GooD-NTS it's related to people that are using prop editor from method that was created before OpenIv make us able to read that kind of file.
    It permit to build this file ( for addonprops ) in an easy and fast way.

    The only convenient is that instead of getting name of prop once the file is rebuild, we got hash code (when opening the file with metatool since openIv can't), wich must also be the reason we can't open it with your new feature.
    Would be really a good thing to get a compatibilty fix to edit this file with OpenIV cause prop editor is a nice and usefull tool but miss some function that we could add ourself if only OpenIv was able to convert it ;S (it's just hardcore to find wich hash is wich prop for big addonprop )
    Or may OpenIv team could release a such program with all possible function.
    I talked of that to method but unfortunatly he don't feel to redo all the program now ;S

    Indeed. If you want more addonprops, you'll need to change the hash name inside the ytyp file. And for that you'll need to be able to open it. Since MetatoolKit still produces a valid ytyp file (as the maps load just fine in game), I see no reason why OpenIV should not be able to accommodate for the small (but non-essential) incongruences between the formats.


Log in to reply
 

Looks like your connection to GTA5-Mods.com Forums was lost, please wait while we try to reconnect.