1.8.6 troubleshooting faq

[RiShooty]

I now am happy to announce my final contribution to 1.8.6. A readme for my pack, but also a troubleshooting faq for all things 1.8.6 that I've learned over the years. No more remade pack releases, but links and help on how to make packs yourself. The reason being, releasing the 1.8.6+snowberry pack and the reformatted jHRP caused too much trouble and too much hassle to even get them approved. Because of this I even got criticized by someone who didn't even see what happened on the original forums when I was trying to find something out for myself with no plan to release it anyway.[you know who you are]. I simply can't deal with this anymore and I feel bad for any damage could have potentially caused, though i have been keeping tech support to my thread only successfully . So all I can really do left is to release a troubleshooting faq to fix any remaining issues not solved by my pack and so people can make packs for themselves as opposed to releasing it and causing a hassle.
------------------------------------------------------------------------------------------------------
Jdoom 1.8.6+Snowberry repack by RiShooty

Because this is also a troubleshooting faq for anything 1.8.6, feel free to reccomend anything to add.
------------
INSTALLATION
------------

1. Simply install it to anywhere you want. Program Files is an easy example.
2. Create a shortcut to snowberry.
3. Load snowberry and follow the instructions to assign your WAD paths. [make sure you do Hexen expansion
backwards!, see below.]
4. If it doesn't pop up with the setup wizard, simply go to Tools and then setup wizard at the top
of the snowberry window.

Enjoy

------------------
COMPATIBILITY LIST
------------------
-Works with any .box as long as it doesn't go over the file limit thats a little over 60. [abbs pack, dreadus'
shotgun]
-works with the latest jdrp and jhrp, already included in .pk3 form and has the necessary deds and manifest so
theyre ready to use.
-Does not work with: jdoom hi-res beta 6 preview pack[can work with the deletion of one file, see bottom],
semireal/episode one skybox, skyglow, any .box that is over the command line's file limit [jdrp.box, jhrp.box]

And then it works with pretty much everything else.

-----------------------------------------------
TROUBLESHOOTING[also for kickstart 1.8.6 users]
-----------------------------------------------
1.0 Hexen Expansion Important Note!
1.1 Windows 7 Users
1.2 Reccomended Video Card Settings
1.3 Multiplayer/LAN
1.4 Addon Tutorials
1.5 Credit/Thanks




1.0 Hexen Deathkings of the Dark citadel Must know
__________________________________________________
When snowberry asks you to assign your wads for Hexen's expansion, put hexen in the place it asks for hexdd and
vice versa. If you put the files in their correct places it just loads up normal hexen for some reason.

1.1 Windows 7 Users
___________________
As of making this readme/troubleshooting file, windows 7 beta does not have opengl yet. To solve this, just
make sure that doomsday is running in direct 3d.

1. Start up snowberry.
2. Go to shared settings
3. click settings tab
4. Click the drop down box next to "renderer library" and change it from opengl to direct 3d. Enjoy.

If you feel running in direct 3d needs a performance boost, try turning on triple buffering in the same page
that you switch from opengl to direct 3d. Only do this if you don't have a consistent framerate and is very
choppy.

1.2 Reccomended Video Card Settings
___________________________________
1. Make sure threaded optimization is off! This is the most important one.
2. If you're getting slowdown, crashing in game or on exit, or just want better gameplay in general,
try forcing vsync with your video card. It runs much better than doomsday's built in vsync. Other alternatives are
-forcing vsync off
-forcing triple buffering[can be more fps unstable, but at least helps prevent crashing.]
3. Not a video card setting, but make sure your memory allocation is maxed out. For kickstart there is an option,
for snowberry it is already preset in this pack as "-m 256m". Go to the developer window when configuring
shared settings.

But yeah I highly reccomend you just force vsync with your video card, vsync off only if your someone who doesn't
like it and have a high enough refresh rate monitor to prevent tearing.

1.3 Multiplayer/LAN
___________________
In multiplayer, make sure you have your ports forwarded of course. The usual 13209 tcp and udp. If you are
not running behind a firewall/router security, you can just set your port to 0. For example, when doing a LAN game,
if you don't have any ports forwarded and are joining a game, make sure you have your port set to 0. Otherwise
it will just exit the game for some reason. This is unless of course you have your ports forwarded. Check your
router settings to do this, i reccomend portforward.com for general instructions for your router.

Another thing to note is that if the server host decides the end the game it might crash, so hosts, dont be
suprised if you have to use ctrl alt delete to exit.

1.4 Addon Tutorials
___________________
As of this post, I won't be releasing anything anymore because I have caused enough trouble as it is. The only
thing I might possibly do is update this readme/troubleshooting file, but that's it. Sure you might want a
compact jdrp alpha 1.1 or use the kick ass hi res textures beta 6 preview pack sucessfully in 1.8.6, but I'm
afraid I cannot give them to you. However i can give you links on how to make your own .pk3s and .boxes and tell
you what to be aware of when using .boxes.

Pk3s:
http://www.dengine.net/dew/index.php...#Creating_PK3s

Sometimes Pk3's need manifests or special .deds to go with them.
manifest:http://www.dengine.net/dew/index.php?title=Manifest


My tutorial for a general .ded for a .pk3:
___________________________________
"3. Creating jHRP.ded.
---------------------
This was the longest, most time consuming work of all.
-made a copy of jDRP.ded.
-Made the couple of naming changes as usual: title, description, model path, beginning of
ded list. Of course the usual changing from doom to heretic. The important part being:
____________________________________
"ModelPath "data/jheretic/ShineMaps"
____________________________________
-Deleted every include command and category of doom, and just made one big category called
everything instead.
-I read down the list of pk3s within jHRP and typed the include command for each
and every one of them. For example:
_______________________________
# jHRP Packs
# =============================

# Everything
Include "A-ClawEnergy.ded";
Include "A-ClawOrb.ded";
Include "A-EtherealArrows.ded";
Include "A-EtherealQuiver.ded";
Include "A-HellGreater.ded";
Include "A-HellLesser.ded";
Include "A-MacePile.ded";
Include "A-MaceSphere.ded";
Include "A-RodFlame.ded";
Include "A-RodInferno.ded";
Include "A-WandCrystal.ded";
Include "A-WandGeode.ded";
Include "Decor-decor.ded";
_______________________________
... and so on.
-After only so much typing, it is finally done.
_______________________________________________"

And then to make sure that the ded is read put
"Include "[your new ded].ded";" at the end of the main ded of the game you want to use it in. [jdoom.ded]
__________________________________________________ __________________________________________________ _____

.boxes:
http://www.dengine.net/dew/index.php?title=Addon_box

*IMPORTANT! When making a .box in mind for 1.8.6, try to use as little files as possible. The entire reason why
the newer .boxes dont work except for abbs pack and dreadus' classic shotgun is because 1.8.6 has a smaller
.pk3 limit, and when it goes over that limit it either crashes by/or compensating for it by leaving out
important doomsday files or even the iwad sometimes. It can take only so many files being loaded into the console
really. The limit is a little over 60, and even then it may not run very well. So when you make your .boxes
try to at least keep it to a decent amount so that everything loads and that it doesnt crash from unstability, as
in try not to go to the limit.

One more tutorial from me. If you wanna use kurikai's awesome looking texture pack for beta 6, all you have to do
is to go into the .pk3 and delete: dhtp-shinmaps.ded. All that file really does is show off beta 6's nice lighting
effects. beta 6 lighting or not, they're still great textures :].

1.5 Credit/Thanks
_________________
Credit goes to the dengdevelopers for making this awesome doom source port and to everyone who has ever helped me
on NewDoom/Offical Doomsday forums. I give my thanks to them, but most of all DaniJ. I thank him for his amazing
amount of paitience and understanding when dealing with my misunderstandings and mistakes, and I sincerely
apologize for anything I might have potentially done to hurt DE development :[. You know I wouldn't have made this
repack and this 1.8.6 trouble shooting faq if I didn't absolutely love your port and I couldn't wait for 1.9.0
to come out of beta .

[RiShooty]

My repack has now been updated with this readme http://rapidshare.com/files/28284539...6_update1_.exe

[Bl4ck0p5]

I'm a newcomer to Doomsday, but there is a serious problem. whenever I load up any game (I only have the DOOM games), the screen looks like...how do I put this...it looks like pixelated vomit. I can load up a game just fine, except the GAME looks like pixelated vomit, too! This happens with all games I try to run on any engine utilizing OpenGL, and it's annoying as Hell! If you, or anybody else, has a solution to my problem, I'd appreciate it very much!

[RiShooty]

0.o That's a new one. Try updating your drivers? If you can tell me your video card I can help you look for one. It could also be your settings, but let's try this first. If neither an update or a settings change works, then I guess you can try direct3d and triplebuffering if you have to.

[RiShooty]

Ohh also, what resource packs are you running? Someone recently had an issue on my other thread that was caused by him running the wrong resource pack for the wrong game.

[RiShooty]

I have an update:

I'm getting better performance when I the anisotropic filtering of the nvidia control panel as opposed to doomsdays. Try it.

[RiShooty]

use the anisotropic*