Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Porting Kit 2.9.0 Released!
47 views
Skip to first unread message
Ezra Lees
Dec 26, 2023, 10:53:48 PM12/26/23
to
Technically, the original Fable game wasn't released on PC either, but we did have an extended port/enhanced port/re-release of it called Fable: The Lost Chapters and a remake of said port called Fable: Anniversary.
Porting Kit 2.9.0 released!
Download Zip https://t.co/63Mk6zJZUM
Fable: Anniversary was a remake of Fable: The Lost Chapters using the Unreal Engine 3 for the XBOX 360. It featured vastly improved presentation, a slightly updated alignment system, vastly quicker loading times, an optional controlled scheme which was more similar to Fable II and Fable III, DLC (mostly joke armor and weapons), achievements, and a changed UI. The PC version had some additional changes; achievements were changed to reflect platform differences, aging was reduced/slowed/something like that by 50%, and in addiction to the standard "Chicken Mode" (how Fable was originally) there was a "Heroic Mode" (a much harder version of the game). The DLC was released in two bundles (instead of multiple packs) for the PC version as well. Finally, the PC version included Steam workshop support and had a free DLC made containing tools for modding and for launching the game with mods.
This is where I think Nintendo could make a lot of money while quenching the thirst for an enthusiast Nintendo experience. Microsoft and Sony are showing that the PC market is not a market that will necessarily threaten your core business. If Nintendo went the Sony route and tried porting some games to PC a year after launch I think they would find similar success. That would undoubtedly lead to a second wave of sales.
Wireless local number portability (WLNP) has been available in the U.S. since November 2003 (in the top 100 Metropolitan Statistical Areas (MSAs)) and May 2004 (in the rest of the country). A consumer wishing to port a number should contact the prospective new carrier, who will start the process of porting by contacting the consumer's current carrier. Commission rules require carriers to port a number when they receive a valid request, and carriers may not refuse to port. However, consumers are still legally bound by their existing service agreements and should be familiar with any fees they may incur for canceling an existing contract before deciding to port a number to a new carrier.
A colleague of mine recently ran into a problem where a process that had supposedly died was still bound to a network port, preventing other processes from binding to that port. Specifically, netstat -a -b was reporting that a process named System with PID 4476 had port 60001 open, except no process with PID 4476 existed, at least as far as I could tell.
If your program spawned any processes while it was running, try killing them. That should cause its process record to be freed and the TCP port to be cleaned up. Apparently windows does this when the record is released not when the process exits as I would have expected.
.NET Core is the future of .NET! Version 4.8 of the .NET Framework is the last major version to be released, and Microsoft has stated it will receive only bug-, reliability-, and security-related fixes going forward. For applications where you want to continue to take advantage of future investments and innovations in the .NET platform, you need to consider porting your applications to .NET Core. Also, there are additional reasons to consider porting applications to .NET Core such as benefiting from innovation in Linux and open source, improved application scaling and performance, and reducing licensing spend. Porting can, however, entail significant manual effort, some of which is undifferentiated such as updating references to project dependencies.
The Porting Assistant for .NET differs from other tools in that it is able to assess the full tree of package dependencies, not just incompatible APIs. It also uses solution files as the starting point, which makes it easier to assess monolithic solutions containing large numbers of projects, instead of having to analyze and aggregate information on individual binaries. These and other abilities gives developers a jump start in the porting process.
Analyzing and porting an application
Getting started with porting applications using the Porting Assistant for .NET is easy, with just a couple of prerequisites. First, I need to install the .NET Core 3.1 SDK. Secondly I need a credential profile (compatible with the AWS Command Line Interface (AWS CLI), although the CLI is not used or required). The credential profile is used to collect compatibility information on the public APIs and packages (from NuGet and core Microsoft packages) used in your application and public NuGet packages that it references. With those prerequisites taken care of, I download and run the installer for the assistant.
Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit (GPTK) combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12[1]. This is a less user-friendly method of installing Windows games on Apple Silicon Macs compared to CrossOver or Parallels, however it unlocks the ability to play many DirectX 12 games. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2,[2] e.g. The Last of Us Part I.
next you install the porting toolkit itself and you should be good to move onto the Wine Prefix section in this guide, keep in mind it might fail the first time or two , but it might just need a retry; if it still doesn't work after a couple tries please report issues to -wine/issues
Keep in mind instead of brew --prefix you will need to replace it with the wine from macports path,/opt/local/libexec/game-porting-toolkit/bin/wine64 ;and gameportingtoolkit itself should be in path and if not its under /opt/local/bin/gameportingtoolkit
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer. It can take over 1 hour to complete depending on the speed of your Mac. This step depending on specs may take around 75 minutes on M1 to 36 minutes on M2 Max.
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer. It can take over 1 hour to complete depending on the speed of your Mac.
A defect of gameportingtoolkit is that it only takes two arguments: the prefix and the exe path. This disallows passing any extra argument (e.g. a -dx11 or -debug_mode flag) to your exe; going back to the real wine64 program removes this restriction. A custom shell function can be used to simplify the wine64 call:
Doom is one of the most widely ported video games.[1] Since the original MS-DOS version, it has been released officially for a number of operating systems, video game consoles, handheld game consoles, and other devices. Some of the ports are replications of the DOS version, while others differ considerably, including modifications to the level designs, monsters and game engine, with some ports offering content not included in the original DOS version.
Doom was ported to IRIX during the summer of 1994 by Dave D. Taylor. IRIX Doom was originally based on the unreleased MS-DOS version 1.5, though later updates were based on versions 1.6 and 1.8. No effort was made to take advantage of SGI's advanced graphics hardware, and like many other ports the game was rendered entirely in software rendering mode.
Doom for Mac was released on November 4, 1994.[citation needed] The Ultimate Doom, Doom II, and Final Doom were ported by Lion Entertainment and released by GT Interactive using a Mac OS launcher application to run original PC WADs. The Mac version runs on System 7 through Mac OS 9 and requires a 68040 or PowerPC processor. Although it can run in Classic under Mac OS X on Power Macs, Panther and Tiger cause graphic artifacts due to the later version of Classic having a double-buffered screen. It can also be played under emulation on Intel and Apple silicon Macs with SheepShaver and QEMU. In addition to an adjustable viewport, it supports rendering at low or high resolutions, and allows network play over AppleTalk as well as IPX.
The source code to the Linux version of Doom was released by id Software on December 23, 1997, under a non-profit End user license agreement; it was re-released on October 3, 1999, under the terms of the GPL-2.0-or-later license. However, the source code to the DOS and Windows versions of the game were not released, due to copyright issues concerning the sound library used by original DOS version and id Software having no access to the source code of the Windows port.[4]
The first version of Doom for Windows was released under the name Doom 95, on August 20, 1996. It was compatible with Windows 95 and up, and was able to use WADs from the DOS versions. It also allowed users to set up multiplayer games much easier than in DOS. It was included with Final Doom. The port was project-led by Gabe Newell and other later founders of Valve.[5]
On September 26, 2001, Doom Collector's Edition was released, containing The Ultimate Doom, Doom II, and Final Doom. It was re-released on January 1, 2004[6] with added preview content for Doom 3. Some early versions of Doom 3 included the Collector's Edition and a small demon figurine as a bonus. The BFG Edition of Doom 3, released on October 15, 2012, includes The Ultimate Doom as well as Doom II.
AcornDoom was released for the Acorn Archimedes by R-Comp Interactive on February 7, 1998.[7] It was made available in a bundle of three Doom games: The Ultimate Doom, Doom II, and Master Levels for Doom II, as well as the Maximum Doom add-on pack,[8] which contains over 3,000 user levels.[9]
0aad45d008
Porting Kit 2.9.0 released!
Download Zip https://t.co/63Mk6zJZUM
Fable: Anniversary was a remake of Fable: The Lost Chapters using the Unreal Engine 3 for the XBOX 360. It featured vastly improved presentation, a slightly updated alignment system, vastly quicker loading times, an optional controlled scheme which was more similar to Fable II and Fable III, DLC (mostly joke armor and weapons), achievements, and a changed UI. The PC version had some additional changes; achievements were changed to reflect platform differences, aging was reduced/slowed/something like that by 50%, and in addiction to the standard "Chicken Mode" (how Fable was originally) there was a "Heroic Mode" (a much harder version of the game). The DLC was released in two bundles (instead of multiple packs) for the PC version as well. Finally, the PC version included Steam workshop support and had a free DLC made containing tools for modding and for launching the game with mods.
This is where I think Nintendo could make a lot of money while quenching the thirst for an enthusiast Nintendo experience. Microsoft and Sony are showing that the PC market is not a market that will necessarily threaten your core business. If Nintendo went the Sony route and tried porting some games to PC a year after launch I think they would find similar success. That would undoubtedly lead to a second wave of sales.
Wireless local number portability (WLNP) has been available in the U.S. since November 2003 (in the top 100 Metropolitan Statistical Areas (MSAs)) and May 2004 (in the rest of the country). A consumer wishing to port a number should contact the prospective new carrier, who will start the process of porting by contacting the consumer's current carrier. Commission rules require carriers to port a number when they receive a valid request, and carriers may not refuse to port. However, consumers are still legally bound by their existing service agreements and should be familiar with any fees they may incur for canceling an existing contract before deciding to port a number to a new carrier.
A colleague of mine recently ran into a problem where a process that had supposedly died was still bound to a network port, preventing other processes from binding to that port. Specifically, netstat -a -b was reporting that a process named System with PID 4476 had port 60001 open, except no process with PID 4476 existed, at least as far as I could tell.
If your program spawned any processes while it was running, try killing them. That should cause its process record to be freed and the TCP port to be cleaned up. Apparently windows does this when the record is released not when the process exits as I would have expected.
.NET Core is the future of .NET! Version 4.8 of the .NET Framework is the last major version to be released, and Microsoft has stated it will receive only bug-, reliability-, and security-related fixes going forward. For applications where you want to continue to take advantage of future investments and innovations in the .NET platform, you need to consider porting your applications to .NET Core. Also, there are additional reasons to consider porting applications to .NET Core such as benefiting from innovation in Linux and open source, improved application scaling and performance, and reducing licensing spend. Porting can, however, entail significant manual effort, some of which is undifferentiated such as updating references to project dependencies.
The Porting Assistant for .NET differs from other tools in that it is able to assess the full tree of package dependencies, not just incompatible APIs. It also uses solution files as the starting point, which makes it easier to assess monolithic solutions containing large numbers of projects, instead of having to analyze and aggregate information on individual binaries. These and other abilities gives developers a jump start in the porting process.
Analyzing and porting an application
Getting started with porting applications using the Porting Assistant for .NET is easy, with just a couple of prerequisites. First, I need to install the .NET Core 3.1 SDK. Secondly I need a credential profile (compatible with the AWS Command Line Interface (AWS CLI), although the CLI is not used or required). The credential profile is used to collect compatibility information on the public APIs and packages (from NuGet and core Microsoft packages) used in your application and public NuGet packages that it references. With those prerequisites taken care of, I download and run the installer for the assistant.
Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit (GPTK) combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12[1]. This is a less user-friendly method of installing Windows games on Apple Silicon Macs compared to CrossOver or Parallels, however it unlocks the ability to play many DirectX 12 games. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2,[2] e.g. The Last of Us Part I.
next you install the porting toolkit itself and you should be good to move onto the Wine Prefix section in this guide, keep in mind it might fail the first time or two , but it might just need a retry; if it still doesn't work after a couple tries please report issues to -wine/issues
Keep in mind instead of brew --prefix you will need to replace it with the wine from macports path,/opt/local/libexec/game-porting-toolkit/bin/wine64 ;and gameportingtoolkit itself should be in path and if not its under /opt/local/bin/gameportingtoolkit
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer. It can take over 1 hour to complete depending on the speed of your Mac. This step depending on specs may take around 75 minutes on M1 to 36 minutes on M2 Max.
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer. It can take over 1 hour to complete depending on the speed of your Mac.
A defect of gameportingtoolkit is that it only takes two arguments: the prefix and the exe path. This disallows passing any extra argument (e.g. a -dx11 or -debug_mode flag) to your exe; going back to the real wine64 program removes this restriction. A custom shell function can be used to simplify the wine64 call:
Doom is one of the most widely ported video games.[1] Since the original MS-DOS version, it has been released officially for a number of operating systems, video game consoles, handheld game consoles, and other devices. Some of the ports are replications of the DOS version, while others differ considerably, including modifications to the level designs, monsters and game engine, with some ports offering content not included in the original DOS version.
Doom was ported to IRIX during the summer of 1994 by Dave D. Taylor. IRIX Doom was originally based on the unreleased MS-DOS version 1.5, though later updates were based on versions 1.6 and 1.8. No effort was made to take advantage of SGI's advanced graphics hardware, and like many other ports the game was rendered entirely in software rendering mode.
Doom for Mac was released on November 4, 1994.[citation needed] The Ultimate Doom, Doom II, and Final Doom were ported by Lion Entertainment and released by GT Interactive using a Mac OS launcher application to run original PC WADs. The Mac version runs on System 7 through Mac OS 9 and requires a 68040 or PowerPC processor. Although it can run in Classic under Mac OS X on Power Macs, Panther and Tiger cause graphic artifacts due to the later version of Classic having a double-buffered screen. It can also be played under emulation on Intel and Apple silicon Macs with SheepShaver and QEMU. In addition to an adjustable viewport, it supports rendering at low or high resolutions, and allows network play over AppleTalk as well as IPX.
The source code to the Linux version of Doom was released by id Software on December 23, 1997, under a non-profit End user license agreement; it was re-released on October 3, 1999, under the terms of the GPL-2.0-or-later license. However, the source code to the DOS and Windows versions of the game were not released, due to copyright issues concerning the sound library used by original DOS version and id Software having no access to the source code of the Windows port.[4]
The first version of Doom for Windows was released under the name Doom 95, on August 20, 1996. It was compatible with Windows 95 and up, and was able to use WADs from the DOS versions. It also allowed users to set up multiplayer games much easier than in DOS. It was included with Final Doom. The port was project-led by Gabe Newell and other later founders of Valve.[5]
On September 26, 2001, Doom Collector's Edition was released, containing The Ultimate Doom, Doom II, and Final Doom. It was re-released on January 1, 2004[6] with added preview content for Doom 3. Some early versions of Doom 3 included the Collector's Edition and a small demon figurine as a bonus. The BFG Edition of Doom 3, released on October 15, 2012, includes The Ultimate Doom as well as Doom II.
AcornDoom was released for the Acorn Archimedes by R-Comp Interactive on February 7, 1998.[7] It was made available in a bundle of three Doom games: The Ultimate Doom, Doom II, and Master Levels for Doom II, as well as the Maximum Doom add-on pack,[8] which contains over 3,000 user levels.[9]
0aad45d008
0 new messages