schkerke.com

Game: Dungeon Siege
Runs on Windows 10: With No Modifications
Notes: Does not include Legends of Aranna

This is for the Steam version of Dungeon Siege but is applicable if you know how to add launch options to your particular launcher.

Right click on the Dungeon Siege game name in the Steam library and choose Properties.

From the window which appears, click the Set Launch Options button.

In the screen which appears enter the following text:

width=1920 height=1080 fullscreen=true vsync=false maxfps=60 nointro=true bltonly=true

width=1920 sets the width of the game screen; replace 1920 with your desired width.

height=1080 sets the height of the game screen; replace 1080 with your desired width.

fullscreen=true turns on full screen mode.

vsync=false turns off vertical syncing. This can help with FPS flutters.

maxfps=60 sets a maximum number of frames per second.

nointro=true turns off the introductory video screens.

bltonly=true turns on BLT mode instead of flip. (See DirectX documentation for further details.) Specifically, this handles a situation where nVidia cards flash.

zonematch=true (see screenshot) will, by default, open the multiplayer menu for you to connect.

Although Dungeon Siege was considered highly moddable at the time, it doesn’t appear that any high definition graphics packs were created or survived.

When you start the game you’ll get an error message about the resolution not matching the hardware configuration. Ignore it.

Once you’re in game you want to hit Escape, then Options. Turn on All Complex shadows and set Texture Filtering to Trilinear. Next, crank up the Object Detail as far as it’ll go.

This video represents all of these settings.

You’ll need to use NuGet to install the Microsoft.TeamFoundationServer.ExtendedClient library before anything:

Install-Package Microsoft.TeamFoundationServer.ExtendedClient

1	Install-Package Microsoft.TeamFoundationServer.ExtendedClient

Then the following code:

using Microsoft.TeamFoundation.WorkItemTracking.WebApi;
using Microsoft.TeamFoundation.WorkItemTracking.WebApi.Models;
using Microsoft.VisualStudio.Services.Common;
using Microsoft.VisualStudio.Services.WebApi;
using System;
using System.Collections.Generic;
using System.Linq;

public class Tfs
{
        public Tfs()
        {
        }

        public List<WorkItem> ExecuteQuery(string teamProjectName, string folderName, string queryName)
        {
            VssConnection connection                        = new VssConnection(new Uri(Configuration.CollectionUrl), new VssCredentials());
            WorkItemTrackingHttpClient witClient            = connection.GetClient<WorkItemTrackingHttpClient>();
            // Note the depth: 2 -- this limits us to two levels of results.
            List<QueryHierarchyItem> queryHierarchyItems    = witClient.GetQueriesAsync(teamProjectName, depth: 2).Result;
            QueryHierarchyItem folder                       = queryHierarchyItems.FirstOrDefault(qhi => qhi.Name.Equals(folderName));
            List<WorkItem> returnValue                      = new List<WorkItem>();

            if (folder != null)
            {
                QueryHierarchyItem query = null;
                if (folder.Children != null)
                    query = folder.Children.FirstOrDefault(qhi => qhi.Name.Equals(queryName));

                if (query == null)
                    throw new ArgumentException(String.Format("Either folder name ({0}) or query name ({0}) are invalid.", folderName, queryName));

                WorkItemQueryResult result = witClient.QueryByIdAsync(query.Id).Result;

                if (result.WorkItems.Any())
                {
                    int skip = 0;
                    const int batchSize = 100;

                    IEnumerable<WorkItemReference> workItemRefs;
                    do
                    {
                        workItemRefs = result.WorkItems.Skip(skip).Take(batchSize);

                        if (workItemRefs.Any())
                        {
                            List<WorkItem> workItems = witClient.GetWorkItemsAsync(workItemRefs.Select(wir => wir.Id)).Result;
                            returnValue.AddRange(workItems);
                        }

                        skip += batchSize;
                    }
                    while (workItemRefs.Count() == batchSize);
                }
                else
                {
                    throw new InvalidOperationException(String.Format("Query ({0}) in folder ({1}) returned no work items.", queryName, folderName));
                }
            }

            return returnValue;
        }

using Microsoft.TeamFoundation.WorkItemTracking.WebApi;

using Microsoft.TeamFoundation.WorkItemTracking.WebApi.Models;

using Microsoft.VisualStudio.Services.Common;

using Microsoft.VisualStudio.Services.WebApi;

using System;

using System.Collections.Generic;

using System.Linq;

public class Tfs

{

public Tfs()

{

}

public List<WorkItem> ExecuteQuery(string teamProjectName, string folderName, string queryName)

{

VssConnection connection = new VssConnection(new Uri(Configuration.CollectionUrl), new VssCredentials());

WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>();

// Note the depth: 2 -- this limits us to two levels of results.

List<QueryHierarchyItem> queryHierarchyItems = witClient.GetQueriesAsync(teamProjectName, depth: 2).Result;

QueryHierarchyItem folder = queryHierarchyItems.FirstOrDefault(qhi => qhi.Name.Equals(folderName));

List<WorkItem> returnValue = new List<WorkItem>();

if (folder != null)

{

QueryHierarchyItem query = null;

if (folder.Children != null)

query = folder.Children.FirstOrDefault(qhi => qhi.Name.Equals(queryName));

if (query == null)

throw new ArgumentException(String.Format("Either folder name ({0}) or query name ({0}) are invalid.", folderName, queryName));

WorkItemQueryResult result = witClient.QueryByIdAsync(query.Id).Result;

if (result.WorkItems.Any())

{

int skip = 0;

const int batchSize = 100;

IEnumerable<WorkItemReference> workItemRefs;

{

workItemRefs = result.WorkItems.Skip(skip).Take(batchSize);

if (workItemRefs.Any())

{

List<WorkItem> workItems = witClient.GetWorkItemsAsync(workItemRefs.Select(wir => wir.Id)).Result;

returnValue.AddRange(workItems);

}

skip += batchSize;

}

while (workItemRefs.Count() == batchSize);

}

else

{

throw new InvalidOperationException(String.Format("Query ({0}) in folder ({1}) returned no work items.", queryName, folderName));

}

return returnValue;

}

Line 17 sets up the VssConnection which is used for multiple comman. Line 18 sets up the WorkItemTrackingClient (witClient). Line 20 retrieves the folder hierarchy; line 21 picks out the folder we specified. Line 22 sets up the returnValue for the procedure.

After that processing is fairly linear. We execute the query (and throw an exception if there’s no results). We pull down batchSize number of work items each time through the loop. Skip is used to track how many we’ve already snagged and should bypass on the next loop through.

Next up: pulling changesets based on their relationship to work items.

Amazon Associates now available in Missouri

Improve Dungeon Siege’s Graphical Resolution

TFS: Execute Query and Return a List of Work Items

Recent Posts

Archives

Categories

Links

Amazon Affiliate Notice

Meta