Strange, just tested. Works fine for me. Did you edit a default playfield.yaml or a playfield_dynamic.yaml. One thing: Did you exit the property before saving. Which means: You need to click into another property's field before saving. Because the properties only update correctly when you leave the control. If this doesn't work: Can you upload the playfield file renamed to txt here? Otherwise you can't upload it. /jmc
1. I saved the updated file, and exited the editor. 2. I didn't edit the "default playfield.yaml, I edited one that was given to me from another user weeks ago. However, before opening in the editor, the sky was fine. Now, the sky resets on all my .yaml files for playfields to white/black. When it gets dark in the game, everything whitewashes, and turns monochrome. All I edited in the editor was the POI's, nothing else... This is for my scenario, playfield is for Reach. Scenario: https://steamcommunity.com/sharedfiles/filedetails/?id=1610229683
OK, just subscribed to your scenario. But I did not get any download in my content/scenarios folder. That's a bit odd, but I started a fresh game on Reach anyway to test it out. The sky in the palyfield copied to the savegame is indeed white. Other than the one you sent me. So editing in EPD works fine as far as I can tell. I'm pretty sure there's something strange going on in conjunction with the subscribed/published scenario. Not sure what this is though. Maybe you can't edit an already published scenario directly. I think the game pulls the files from the workshop instead of the scenario folder. I would suggest trying to copy the 'HALO - Source -_xxxxxx' to another folder in your scenarios folder. Maybe just 'HALO Test' and edit and try a fresh game with those files. /jmc
Not sure where this is for you, but when I sub to a scenario, I can edit it here: It will never show up in the scenarios folder when downloaded from steam, unless manually added.
However, for me, as the author, the scenario is here: If I move, rename, or edit this, it will disconnect from steam, and I'll have to upload it as a New Scenario again...
Ok, found it in there. Never tried that before. Those files in there indeed all have a SkyColor of 1,1,1. But when I edit and save them, they get saved correctly and I can open them again and the color has been saved correctly. Does it save the file for you, if you edit it? Other than changing the playfield file, EPD also generates a backup file in the folder with a DateTime stamp. Something like this: /jmc
And no.... I haven't changed a thing. It just gave me the big Finger last night for some reason I guess. - sigh -
Well strange. Glad it works now. If it doesn't, keep me posted. The only explanation I could possibly have, is that it still has something to do with the workshop. But I have no clue, if and how this could be affecting playfield editing with EPD. As long as you keep the backups and save regularly, nothing should be lost. /jmc
Ok. Just re-uploaded and updated the scenario. The sky looks perfect, just as it should. Anyone feel like testing and telling me otherwise?
If it happens again, try setting the Atmosphere Parameters to [1, 1.6] (game default). If it's an older .yaml it won't have AtmosphereParams at all because the option didn't exist before Alpha 9. So the EPD may create that option and set it to [0, 0], which would wash out the sky as you described.
Downloaded scenarios never go to the Content/scenario folder but to the workshop downloads folder with there ID. Same map as downlaoded BPs
@jmcburn Could the EPD have an 'enabled' check box for Atmosphere Parameters ,or some type of statement in the programming that says 'If AtmosphereParams does not exist, Then set at [1, 1.6] ?
I think I can initialize it to [1,1.6] If a playfield contains the property, it most likely will overwrite it with it's values, but I'm not sure. I'll take a look. No promises though. /jmc
UPDATE (v1.60.0 b1662) CHANGES: First version of EPB (Blueprint) DetailsBrowser (only in RandomPOIs for now as test) added <Null> (no output) and 'None' (will output) items to dropdowns to differentiate between new Faction:None and empty properties. Please test, if something is broken now with outputting 'None' and no output at all for properties. Initialize AtmosphereParams to [1,1.6] if property does not exist in playfield yet. Pease test, if there are any regressions when saving DOWNLOAD LINK: https://www.dropbox.com/s/9q7qrr3mvv8sqmw/EPD_v1600b1662_public.zip?dl=0 /jmc
You would get SO many 'coolness' points, if you integrated the blueprint reader, and rendered a 3D model .. But for your own sanity's sake, I'd recommend against it Still, cool with more info on BPs! You rock as usual
I guess that would be cool. However, I still try to read the block format based on what's known already, but no real progress there. When I have a STABLE read and write process, maybe some basic editing and displaying could eventually happen, but that all lies very far in the future and no idea, if I ever manage to do so. /jmc
UPDATE (v1.60.1 b1731) CHANGES: added more properties to EPBDetails Browser (SpawnName, FileName, Scenario, Folder) added/showing progressbars while importinge prefabs. DOWNLOAD LINK: https://www.dropbox.com/s/wgs5abzofsrette/EPD_v1601b1731_public.zip?dl=0 IMPORTANT: If somehow EPD crashes during EPB (re)import, please let me know and upload epd.log renamed to .txt here, so I can see, which blueprints still have issues. If you can find the bluprint name in the log that causes the issues, you can upload that as well here. Otherwise I may ask you for the blueprint after I checked the log. /jmc
