rob10

Known issue currently and reported in a few spots.  Try searching BORT as well as board.

ViewportHandling.lua
In the directory:   \DCS World OpenBeta\Scripts\Aircrafts\_Common\Cockpit
You want the command at LINE 33:    dedicated_viewport                   = {3910,2437,600,700}   -- it will have "default...." rather than numbers in yours to start.  The numbers here are what I use, but likely aren't much use to you.
 
This gets wiped on update, and I'm guessing doesn't pass IC if that matters to you.

Make sure you're binding and using the same version of SIM or GAME mode (i.e. if you're using SIM mode, make sure you have the bindings done in SIM not GAME mode).

Assuming you are in the correct column (the one for the mouse), RIGHT click on the setting you want to bind and you'll get a dropdown that you should be able to pick the button from.

SCS LEFT will set the MAV to uncaged and slew to the TGP target.  Make sure you have TDC depressed with TGP DDI active to designate the target.  If it doesn't automatically uncage when you select the MAV DDI, use the cage/uncage button on your HOTAS to uncage it and it should automatically slew to target if it's within gimbal limits (if it's outside limits it will automatically cage).  All of this assumes IR MAV.  Laser MAV is very similar, but a few differences.  Also note that you can't manually slew the MAV while you have a target designated (designated via WPDSG, targetting pod, etc).

Do a search on "track".  You'll find lots of posts.  The short version is it's not a reliable way to record longer and/or more complex missions currently.  ED would like to replace it, but it's not a high priority item currently.

It's because his position is updated based on datalink information provided from his plane to yours.  And unfortunately the datalink updates are relatively slow IRL).  So if you were both standing still it would be perfect.  Because you are both moving and the position shown is the actual position he was at at time of last update it looks like the marker drifts and then jumps to current position on the next update.

Not really.  That's going to be a HUGE task as the basics are TAC and SUPT menu pages (easy enough) but after you select an item on there you're potentially going to have 3-4 levels of pages for some of buttons that you can press beyond that.  For example, select the STORES page, then a loaded JDAM (which actually adds more confusion because the top OSB's change depending what weapons you have loaded), then JDAM DSPLY page, then MSN page.  That's for pre-planned mode but if you're in TOO mode you get a totally different menu's.  You're maybe better off to have it control the individual OSB's by # (i.e. OSB1, OSB2 etc) than trying to define all of the functions at least beyond just the TAC and SUPT pages.
And for your example, even selecting HSI page depends on whether you are currently in the TAC or SUPT page and I'm not aware of any way to consistently select one of those or determine which you are on (i.e. there is no button or command to specifically select TAC or SUPT, you have to press the menu button and it only swaps between the two so without knowing which one you're on you have no way to specify which one you want).  EDITED TO ADD: this is really more of an issue if you happen to start on SUPT page.  If you're in another page already and menu back it should start on TAC page.

It changed around Halloween.  Definitely been requested to give them a little more coffee to increase their pep.

What Lace said.  Make sure you press and hold BEFORE the cue hits the release point and keep holding until it's off the rail.  And currently you need to be very precise or it won't release.
The other thing it might be (been a while since I flew the F-16, but I think this is correct) but with CCRP I think you get 2 "drops" of the release cue -- 1st one is for lofted? delivery and 2nd will be for level flight.  If you're pressing on the 1st drop you might not get release.

Are you assigning them in the AXIS section of the bindings?  At top it will give an option toward the left for "All commands but axis" (or similar) and you need to drop that menu and select AXIS from there to get to the axis assignments.  Sounds like you're binding them as buttons in the regular commands.

Please post a track and someone will likely spot what you're doing wrong.  From your initial description it (no explosion effect) it really sounds like you haven't set the fuzes on the bombs.  If you don't have fuzes set you're just dropping a big chunk of metal.

IIRC HUD won't display time with weight on wheels.
The time on the IFEI (fuel gauge instruments) time starts in LOCAL time.  Hit the ZONE button in the middle between it to change it to ZULU time (marked with Z to the right of it).  The HUD ONLY shows ZULU and can't be changed from that.  Measured Imperative uses ZULU which is why the time in your IFEI is "wrong" (it's not, it's just showing you local time rather than Zulu).
By the way, it's well worth digging into the Time On Target (TOT) functions in the nav system and learning how to use them for this campaign.

So just to double check, you've saved your bindings in SIM, so in that case did you check in your settings and make sure you have UNCHECKED "Game avionics" and "Game flight mode".  Apologies if you already have checked this, but it's the other typical related thing that catches people out with this type of issue (and sometimes people have had them get randomly turned back on when they don't remember messing with them).  If it's not that I don't have any more suggestions.

Nope

Active Pause has been moved to the UI layer rather than in each individual aircraft bindings
And the search button would have been your friend (just searching on ACTIVE would have given you your answer).

Give it 5 minutes and try again.  I just had the same and it took 3 or 4 tries to get it to go through.
And my issue was prior to getting the hotfix update, so it's not directly being caused by it.

The other thing to note in the F-18 is that currently (relatively recently added) if a bullseye is included in the mission it will be automatically assigned to WP 59.  So you should be able to just assign WP 59 as A-A WP in any mission and have a proper bullseye in your flight computer.

Use RESET on OSB 14 of the radar.  That will remove whatever L+S and/or DT2 targets you have assigned.

Did you press the UFC ENTER key after you set the channel?  Sometimes it won't register that you've set the proper channel if you don't.

JDAM with JHMCS: before you designate your first target you'll have the dashed circle with dot in centre targeting symbol when you SCS FWD to select HUD/JHMCS.  After you designate your 1st target this way, you'll have the small broken diamond over the designated target and the JHMCS will have a small cross showing where you're looking.  If you want to move it to a new target with the JHMCS, use NWS button to undesignate. The JHMCS symbology doesn't change but if you put the small cross on the JHMCS over a new target and designate again it will move the designated target to there (broken diamond symbol).  If you DON'T undesignate then attempting a new designate does nothing.  A little confusing since the JHMCS symbology doesn't change back to the big circle with dot targeting symbol after you undesignate so you have to use the small cross to designate a new target and have no indication you've undesignated previous target.  I feel like it used to change back to the circle and dot so you knew you had undesignated but maybe that's always just been with GBU's.
It makes sense as Tholozor says that the broken diamond stays where your original designation was since that's where the JDAM is currently targeted to and that's what it's displaying.  Even if you undesignate, the JDAM still has that point as your target.

That sounds like you're not doing a TDC DEPRESS to designate the target after you slew.  Just moving the TGP doesn't move the target designation after you've set it (i.e. if you WPDSG'd it).

If you're not using EASY comms you need to use the COMM1 or COMM2 switch (at least in the Hornet) rather than the COMMUNICATIONS MENU binding.  COMM MENU works on ground, but not in air.  IIRC this can be forced on in missions/campaigns, so if you normally use EASY whatever mission you're flying may not let you use easy.

Yes.  If MAV is on a DDI even if that DDI isn't priority the FOV controlled is always the MAV.  You need to use OSB's to change things on the TPOD.
 
And as a general comment: please try the search function 1st people.  This particular question gets asked and answered at least once every couple of weeks or less.