How can I fix RptViewer timeout for an ssrs report in vb.net applications?

I have been developing a couple dozen reports within an application for a client over the last several months and initially had to fight with the report timeouts in the server, sql, and client in order to get the reports to properly load.

Some time has passed, and we have changed other areas of the code, but none of the server settings, I use a personal machine that has the database untouched by anyone else. When I attempt to view my largest report in app I get this message after 30 minutes:

An error occurred within the report server database. This may be due to a connection failure, timeout, or low disk condition within the database. (rsReportServerDatabaseError) Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

If I attempt to load the report in browser using localhost/reports/, as well as from SSRS preview, and both methods load perfectly.

I am developing in an entity framework, wcf hosted context based setting using the RptViewer class and basicHttpBinding methods, I have multiple app.configs in my program and have pushed all of their timeouts to above 30 minutes, I set ProcessingMode to Remote, and ServerReport.ReportServerUrl to the web browser address(localhost/reportserverand) and give it a 24 hour timeout(86400000 ms).

The timeout modifications I have added all fall under basicHttpBinding in this manner(name intentionally blanked here):

I have also modified the database timeout settings for remote connections in SQL management studio, and the settings in the web browser general settings when connection to the reports have been set to never time out.

Are there any timeout values I may have missed? The browser and ssrs preview versions run to almost the hour mark, so I don't believe the timeout is occurring within SQL, I've been running the web reports based off Localhost/Reports, but the system connects to Localhost/ReportServer(which takes a lot longer to load when in web browser). I'm wondering if this might be part of the issue, as even the loading icon does not appear for a very long time.

Can anyone point out any key 30 minute default timeouts that I may have missed that I suspect to be within the report server itself when accessed through code? Alternatively, is there an easy way to quickly locate which parameter is timing out?