hdchristopher 11 Posted August 22, 2014 (edited) When I try to generate the layers in terrain Builder I am having this issue Can't load image from file 'P:\': file does not exist. Layers generation - PNGOVerlapV3Style.cpp bool V3PictureDataMod::LoadFromFile( const char* filename = "P:\" ) Unable to open the image file. Layers generation - Unable to load the file "P:\". Everything appears to be setup correctly. This is a fresh install. Here is the layers cfg class Layers { class ofc_strbeach { texture = #(rgb,1,1,1)color(0.5,0.5,0.5,1,cdt); material = "ofc\fiji\data\ofc_strbeach.rvmat"; }; class ofc_strgreengrass { texture = #(rgb,1,1,1)color(0.5,0.5,0.5,1,cdt); material = "ofc\fiji\data\ofc_strgreengrass.rvmat"; }; class ofc_stony { texture = #(rgb,1,1,1)color(0.5,0.5,0.5,1,cdt); material = "ofc\fiji\data\ofc_stony.rvmat"; }; class ofc_concrete { texture = #(rgb,1,1,1)color(0.5,0.5,0.5,1,cdt); material = "ofc\fiji\data\ofc_concrete.rvmat"; }; }; class Legend { picture="ofc\fiji\source\mapLegend.png"; class Colors { ofc_strbeach[]={{230,230}120}; ofc_strgreengrass[]={{50,160,50}}; ofc_stony[]={{0,100,250}}; ofc_concrete[]={{170,70,170}}; }; }; Edited August 22, 2014 by hdchristopher Share this post Link to post Share on other sites
1para{god-father} 105 Posted August 22, 2014 Missing "}" ofc_strbeach[]={{230,230}120}; Should be :- ofc_strbeach[]={{230,230}120}}; Also you can change all texture to: texture =""; That should then do the trick :) Share this post Link to post Share on other sites
hdchristopher 11 Posted August 23, 2014 Thanks for finding that error, but sadly, that didnt fix it. I have also went back to my other maps that worked perfectly before, and now they give me the same error. Share this post Link to post Share on other sites
bushlurker 46 Posted August 23, 2014 It's a Windows/Tools problem - probably something to do with running as "admin" Vs "normal" - it literally isn't finding your P:\ drive.... Thats why ALL your previously working terrains suddenly.... aren't... B Share this post Link to post Share on other sites
hdchristopher 11 Posted August 24, 2014 Well I have run out of ideas on how to fix this problem. It only started after the last update. 1) Added P:\ to the environmental variables path 2) I have tried mapping to a different drive letter. 3) Uninstalled everything Arma and Steam related and re-downloaded it. 4) Even went so far as to wipe out my entire HD and put on a fresh install of windows 7, then re-downloaded all things Arma again, but still get same damn error. 5) Also tried setting the preferences under the tools\settings. Why can it not see my P; drive? Does anybody have any ideas what to try next? Share this post Link to post Share on other sites
Cype_Revenge 651 Posted August 25, 2014 You installed your P drive from Steam? I can only recommend to install the P drive with the tools from Mikero! http://dev.withsix.com/projects/mikero-pbodll/files and an installationvideo : this works perfect for me since months! maybe helps :rolleyes: Share this post Link to post Share on other sites
Tom_48_97 523 Posted August 25, 2014 (edited) It's a Windows/Tools problem - probably something to do with running as "admin" Vs "normal" - it literally isn't finding your P:\ drive.... Thats why ALL your previously working terrains suddenly.... aren't...Fact is mapDisk mounts P for Admins and users. Looks like P is not mounted at all.Well I have run out of ideas on how to fix this problem. It only started after the last update. 1) Added P:\ to the environmental variables path 2) I have tried mapping to a different drive letter. 3) Uninstalled everything Arma and Steam related and re-downloaded it. 4) Even went so far as to wipe out my entire HD and put on a fresh install of windows 7, then re-downloaded all things Arma again, but still get same damn error. 5) Also tried setting the preferences under the tools\settings. Why can it not see my P; drive? Does anybody have any ideas what to try next? Are you able to see you P: drive in the explorer?If yes, are you able to manipulate files? If not, open a command prompt, type "subst", [ENTER] and paste the result here. (twice, with a normal user prompt and an administrator one) [*]Which version of the tools are you using? (stable branch or development (if dev, with or without hot fixes?)) [*]What is your OS? [*]Since when does the problem exist? You installed your P drive from Steam?I can only recommend to install the P drive with the tools from Mikero! http://dev.withsix.com/projects/mikero-pbodll/files and an installationvideo : this works perfect for me since months! maybe helps :rolleyes: If it's a matter of administrator rights, the problem remains unchanged because if you just run "subst p: "someDrive\somePath"", you will mount P only for the current user level. When a drive is substituted with a normal user, administrators won't see it and vice versa. But still a good tutorial if you are sure you have only one user level involved.In the following example, I mounted X: with an administrator account. Windows rights management can be a headache :) http://tom4897.info/wp-content/uploads/2014/08/Subst_adminVsUser1.jpg Edited August 25, 2014 by tom_48_97 Share this post Link to post Share on other sites
Cype_Revenge 651 Posted August 25, 2014 again i learned something here.... Thanks Tom Share this post Link to post Share on other sites
hdchristopher 11 Posted August 26, 2014 (edited) Tom_48_97, I use only an administrator account, no user accounts. Thanks for trying to get me straightened out. :) Here are the answers to your questions: Are you able to see you P: drive in the explorer? Can you manipulate files? Yes open a command prompt, type "subst", [ENTER] Which version of the tools are you using? Stable Branch What is your OS? Windows 7 64 bit Since when does the problem exist? Since last update. Edited August 28, 2014 by hdchristopher Share this post Link to post Share on other sites
hdchristopher 11 Posted August 28, 2014 You installed your P drive from Steam?I can only recommend to install the P drive with the tools from Mikero! http://dev.withsix.com/projects/mikero-pbodll/files and an installationvideo : this works perfect for me since months! maybe helps :rolleyes: Thanks for the thought, but no go. *****UPDATE 8/27/2014***** I have just switched over to my Windows 8 side and installed Arma 3 and Arma 3 tools. Had to use hot-fix bat's to mount P: drive. I then created a small map for test and I get the exact same error on the Windows 8 side Can't load image from file 'P:\': file does not exist. Layers generation - PNGOVerlapV3Style.cpp bool V3PictureDataMod::LoadFromFile( const char* filename = "P:\" ) Unable to open the image file. Layers generation - Unable to load the file "P:\". I also get this error Rvmat conf - LayerRvmatCFG.cpp bool CLayerRvmatCFG::Open( const char* filename = "p:\ofc\fiji\data\gdt_strbeach.rvmat" ) Source file cannot be opened... Rvmat conf - LayerRvmatCFG.cpp bool CLayerRvmatCFG::Open( const char* filename = "p:\ofc\fiji\data\gdt_strgreengrass.rvmat" ) Source file cannot be opened... Rvmat conf - LayerRvmatCFG.cpp bool CLayerRvmatCFG::Open( const char* filename = "p:\ofc\fiji\data\gdt_stony.rvmat" ) Source file cannot be opened... Rvmat conf - LayerRvmatCFG.cpp bool CLayerRvmatCFG::Open( const char* filename = "p:\ofc\fiji\data\gdt_concrete.rvmat" ) Source file cannot be opened... So I dont think it's my operating systems, but something you changed in the latest update 1 Share this post Link to post Share on other sites
hdchristopher 11 Posted September 5, 2014 Anyone else having this issue? Share this post Link to post Share on other sites
thoops99 14 Posted March 30, 2018 On 9/5/2014 at 11:09 AM, hdchristopher said: Anyone else having this issue? yup it was all working the other day but now its not Share this post Link to post Share on other sites
RoF 241 Posted March 30, 2018 12 hours ago, thoops99 said: yup it was all working the other day but now its not Why are you replying to someone from 2014? lol Why not make a post with your issue instead Share this post Link to post Share on other sites