Hi
Just gave the hardware mode version a go and it crashes as soon as i try to start it thinking it was maybe an issues with the settings I opened up the settings.ini in notepad and got this
https://i.postimg.cc/SK2dSss4/untitled.png so it seem that the issue may be that the maxport.exe can't read the file.
The fix however is simple just open up settings.ini in wordpad select all and copy then close wordpad then open settings.ini in notepad select all and paste then save this eliminates what ever it is that stops maxport.exe from reading the file so to avoid issues in future I'd do this for all of the ini files and then if you need to make changes to the ini files I'd do so in notepad.
Ok so now that i've fixed that problem when i load up the hardware version of maxport for some reason I’m getting a blank command prompt window? Question why is the command prompt is being invoked that’s kind of strange, also when I tried to close said window I got the following crash.
https://i.postimg.cc/4NtBWFCX/crash.png Now at first I though this might have something to do with vdm sound because I get the same sort of command prompt window when running 1.04 but then I did a fresh install of max to its own folder rather then just copying my pre-existing install and it still appeared so obviously this is coming from maxport for some reason ???
Second the speed of the hardware version is crazy fast perhaps a little to fast so much so that there isn’t enough time for sequences of events to occur properly for example when attacking with a tank say, both shots happen so fast that they are almost simultaneous which doesn’t leave enough time for the fire sound to play properly so might be an idea to slow things down a touch perhaps add something to the ini file which would let players adjust the game speed.
Also as previously mentioned the sound is messed up but obviously as you already explained this is due to the lack of support for the loop points that are necessary to make the sound work properly so evidently you haven’t found a solution for that just yet.
Another issue with the sound is the volume, there seems to be some weird dynamic sound thing going on and the volume keeps changing one minute its really loud the next its really quiet which makes it tough to set the volume to an appropriate level.
As previously mentioned the colours on the allocation screen seem to be off here are a couple of screen shots to show what I’m seeing the first is 1.04 the second is maxport as you will see the back ground colour for the overlaid text is wrong.
https://i.postimg.cc/QdvNjt4Q/screenshot1.png https://i.postimg.cc/GmTrgRLH/screenshot2.png Now I know that you said that this is due to a defect getting fixed but what I would perhaps suggest is to make the game use the higher quality sample as per the fix but adjust it slightly and make it darker so that it matches the original aesthetic.
Also if you flick back and forth between the 2 screen shots you will notice that the text on the left and at the top seems to be slightly misaligned in 1.04 all the text is centred but on maxport the centring is off
Both minor issues I’ll grant you but the little details like that still matter and neither should be difficult to fix
if you try to move a ground unit on to a tile that is occupied by an aircraft the game misbehaves and gives you the wrong cursor and wont let said ground unit move onto that tile, clearly this is incorrect behaviour.
The same thing happen when trying to move an aircraft on to a tile occupied by a ground unit or structure again the cursor misbehaves and wont let you move there, evidently this defect hasn't been fixed yet.
Trying out the campaign game and when trying to steal the computers units if the infiltrator fails, the infiltration unsuccessful sound doesn’t seem to play, this may be related to the fact that the game is running to quickly and therefore sequences of events don’t have time to happen properly or it could be a coding error.
After a sub engages in an attack if you only fire 1 shot and have movement points left and you then move away out of detection range the sub doesn’t submerge like it should.
Talking of attacking in 1.04 they change the way attacks work so that when you select to attack a target the unit will keep firing until either the unit runs out of shots or the target is destroyed, it would be nice to have the option to have attacks work like they do in 1.03 where you click on a target once and the unit fires once only.
similarly spies incorrectly remain visible for the rest of the turn after attacking or otherwise being detected even when there are no infantry around this is incorrect behaviour if there are no infantry around and the spy moves after attacking or otherwise being detected the spy should become invisible again.
The troop carrier also has a similar issue when transitioning from ground to the water the troop carrier isn’t submerging like it should be this also happens in 1.04
When using full screen mode if you alt tab back to the desktop there is some rather nasty bad behaviour the screen flickers like crazy and the desktop is unresponsive, if you open up task manage and try to end task on max nothing happens, if you try to call up the start menu its immediately closed again if you try to open the menus on task manager they wont open or if they do there instantly closed again.
if using screen mode 2 and you try to alt tab back to the desktop the game doesn’t minimise like it should, which of course makes life difficult when I’m trying to document glitches and I can’t get the game to minimise correctly.
Not sure what’s going on but something isn’t working right, because regardless of the screen mode when I alt tab back to the desktop the game should be minimised as expected and the desktop should be fully functional.
Just tried to reload and got the following error and then the game crashed when I hit debug
https://i.postimg.cc/CL3Lg56j/crash2.png Since I have gotten this error multiple times now and since the game crashes every time I hit the debug button then it might be helpful to have the game create a crash log when it does crash as this would aid in finding and eradicating bugs
The rational behind is that if you have the game dump everything to a text file upon a crash I could then post the crash log and this would help you more easily figure out what it is that’s misbehaving and causing the crash and therefore make it easier to find and eradicate the source of the problem.
I’ve also observed what appears to be some odd decision making by the computer, on 1.04 normally the computer wont come anywhere near my base due to the fact that I have applied the [maxsuper] cheat to all of my units to discourage rush attacks by enhanced scouts which is kind of cowardly and incredibly frustrating when you keep getting taken out within the first 4 or 5 turns every time you start a new game since there simply is no way to defend against that, but on maxport even though the computers scouts don’t stand a chance against my scouts all of which have the [maxsuper] cheat applied the computers scouts are still trying it on and getting instantly destroyed which indicates something in the computers logic isn’t working right because if the computers units don’t stand a chance against me they shouldn’t come anywhere near me if I’m understanding how the computer calculates no go areas due to damage level being to high.
so I'm not convinced that defect 155 is in fact properly fixed if its causing the AI to make decisions that it shouldn't make so for example In this screen shot
https://i.postimg.cc/gjDT1nvR/screenshot1.png you see the 2 blast marks where 2 of the green computers scouts tried to attack me the one on the left going after my builder the other going after my surveyor neither attack ever had any chance of succeeding because the one going after my surveyor didn’t have enough movement points and the one going after my builder was never going to get anywhere close due to the fact the its protected therefore neither attack should have been attempted if the AI logic was working right, so not sure why the computer is doing that but something is off.